This is the mail archive of the
gdb-patches@sourceware.cygnus.com
mailing list for the GDB project.
Re: patch management?
- To: Jim Blandy <jimb at cygnus dot com>
- Subject: Re: patch management?
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Fri, 19 Nov 1999 12:24:43 +1100
- CC: Michael Meissner <meissner at cygnus dot com>, Tom Tromey <tromey at cygnus dot com>, Jason Molenda <jsm at cygnus dot com>, gdb-patches at sourceware dot cygnus dot com
- Organization: Cygnus Solutions
- References: <199911152157.QAA26389@zwingli.cygnus.com> <19991116101108.B23372@tiktok.cygnus.com> <npln7y70lt.fsf@zwingli.cygnus.com> <19991116113818.B1587@cygnus.com> <199911162051.MAA17286@ferrule.cygnus.com> <19991117212650.B11794@tiktok.cygnus.com> <nppux767s7.fsf@zwingli.cygnus.com>
Jim Blandy wrote:
>
> > I'm not familar with Gnats. Ideally something like Clarify's work queues (hey
> > put down those basebats....) where a patch waiting to be reviewed sits in a
> > queue, and people can indicate that they are looking at the patch for those
> > patches that take more than 2 seconds of time to evaluate (so that you don't
> > have 3 people all looking at the patch at the same time) and/or approval. It
> > would be nice if it could work with multiple branches (and especially handle
> > those things that go out into fsf, etc.), hopefully doing the checkin
> > automatically. As a patch reviewer, I want to be able to see all patches that
> > are waiting for me personally to look at, and also patches that anybody in the
> > group can approve. As a patch submitter, I want feedback on outstanding
> > patches.
>
> The CVS stuff is a challenge.
>
> But I think GNATS can do all the rest, just by choosing the right
> conventions. These conventions should be explained somewhere really
> public, like on the GNATS query web page. Every PR should have a
> header named "State-explanations:" whose value is the URL for the web
> page explaining them, so nobody forgets.
On the queue side, Clarify (oh no, not another one :-) allows you put
your tasks into a number of local work-in-progress bins.
Can I do that?
Andrew