This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Using a patch queue?
- From: Bob Rossi <bob_rossi at cox dot net>
- To: gdb at sourceware dot org
- Date: Wed, 29 Mar 2006 23:13:17 -0500
- Subject: Re: Using a patch queue?
- References: <20060330001459.GA13813@nevyn.them.org>
On Wed, Mar 29, 2006 at 07:14:59PM -0500, Daniel Jacobowitz wrote:
> Daniel Berlin offered in February to set up a patch queue. It's some
> custom software that he wrote for GCC, after two consecutive GCC Summits
> in which people agreed that they wanted some automated way to keep track of
> patches, but no one came up with anything that seemed usable.
>
> Here's the GCC one:
> http://www.dberlin.org/patches/
> http://dberlin.org/patchdirections.html
>
> I've never used it except to play with it, but a lot of GCC contributors do,
> as you can see. I think that's a pretty compelling point in its favor,
> since they have a similar workflow to ours.
>
> The patch tracker follows the list (via the web archives, I think) and
> collects annotated messages. You're under no obligation to annotate your
> messages; anyone can manually add a URL to the patch tracker via the web
> interface. I believe the first review response removes the patch from the
> queue; we might want to save :REVIEWMAIL: for final approval/rejection.
> Or it might be useful enough just to track patches which have never
> been looked at, which happens quite a lot.
>
> I wouldn't mind having a better tool than my inbox to track down what needs
> looking at; I don't have enough time to review everything that needs
> reviewing as it is. Anyone else have an opinion?
For what it's worth, I like the idea a lot.
Bob Rossi