This is the mail archive of the
mailing list for the GDB project.
Re: getting patches organized
- To: gdb-patches at sourceware dot cygnus dot com
- Subject: Re: getting patches organized
- From: Tom Tromey <tromey at cygnus dot com>
- Date: 18 Nov 1999 00:55:47 -0700
- Newsgroups: cygnus.patches.gdb
- Organization: Cygnus Solutions
- References: <Pine.LNX.firstname.lastname@example.org>
- Reply-To: tromey at cygnus dot com
>>>>> "Jimmy" == Jimmy Guo <email@example.com> writes:
Jimmy> - the current reviewer (owner) of the patch
Jimmy> - status change history (who, when, what change)
Jimmy> - automatic email notification of any status update to the original
Gnats has these.
Jimmy> - dependency or 'link' sections:
Jimmy> + dependency on a source code base (snapshot, release, cvs export
Jimmy> date, etc.)
Jimmy> + dependency and link to other patches
Jimmy> + link to a problem report, if applicable???
Jimmy> - the web interface with crossing referencing capability (e.g. for
Jimmy> patch dependencies, bug report) through URL, for easy traversal.
These aren't done right now. I'd like to see gnatsweb changed to
recognize URLs in text it is displaying, but I don't know if/when this
Jimmy> - a URL to the patch review process / the new patch tracking system
Jimmy> usage guide to understand what should be expected for a patch at a
Jimmy> given status.
This could probably be easily done by hacking gnatsweb.