Re: getting patches organized

[Jeffrey A Law <law at cygnus dot com>]

  In message <199911172343.SAA28254@zwingli.cygnus.com>you write:
  > 
  > As folks have probably figured out, I'm beginning to have a hard time
  > keeping track of the patches that I'm responsible for reviewing, which
  > patches I have reviewed, whether the submitter has gotten back to me
  > about my comments, etc.
  > 
  > This situation is worsened when some urgent issue appears on some
  > Cygnus project I'm responsible for, and I have to focus on that for a
  > few weeks.  When I come back, it's difficult for me to recover all the
  > state I'd built up before I was drawn away.
  > 
  > It's been suggested that we could use a bug-tracking system like GNATS
  > or Bugzilla as a patch-tracking system.  We'd change the status values
  > to some set like "Awaiting-Review", "Awaiting-Revision", "Approved",
  > "Applied", "Rejected", "Withdrawn", or whatever.
  > 
  > The only system I'm really familiar with is GNATS.  GNATS can
  > automatically stash E-mail conversation related to a patch in the
  > patch record ("PR"), which is exactly what we want.  It's got web
  > interfaces, a decent query ability, and so on.  So I think it would
  > work great.
  > 
  > What would the folks on this list who are actually submitting patches
  > want from such a system?  Certainly all the data would be public.
  > What else should we worry about?
Note that we're looking into setting something similar up for GCC;  we
were going to initially try to deploy something for use internally within 
Cygnus's GCC group first, tune it, then try to deploy it for all GCC patches.

There isn't anything directly designed for patch tracking, but like y'all we
came to the conclusion that packages with do a good job at bug tracking
ought to be adaptable.

Diego -- can you forward that initial summary you sent to the Cygnus GCC team
to the Jim & the GDB folks.

jeff