Using a patch queue?

[Ramana Radhakrishnan]

I think its a good idea as it might enable more people to help track
patches down . Folks tend to try and look at patches but this should
help to not allow stuff to slip through the cracks. 

cheers
Ramana

On Wed, 2006-03-29 at 19:14 -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?
>