getting patches organized

[Jimmy Guo]

>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?

This is a great idea!  I'd like to see:
- the current reviewer (owner) of the patch
- status change history (who, when, what change)
- dependency or 'link' sections:
  + dependency on a source code base (snapshot, release, cvs export
    date, etc.)
  + dependency and link to other patches
  + link to a problem report, if applicable???
- the web interface with crossing referencing capability (e.g. for
  patch dependencies, bug report) through URL, for easy traversal.
- automatic email notification of any status update to the original
  submittor
- a URL to the patch review process / the new patch tracking system
  usage guide to understand what should be expected for a patch at a
  given status.

Maybe I'm asking too much, maybe that's what GNATS can easily handle.
Regardless, I look forward to this system up and running first.

- Jimmy Guo, guo@cup.hp.com