This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Starting to track patches through bugzilla
- From: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- To: Nathanael Nerode <neroden at twcny dot rr dot com>
- Cc: dberlin at dberlin dot org, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- Date: Fri, 26 Sep 2003 22:56:57 +0100 (BST)
- Subject: Re: Starting to track patches through bugzilla
- References: <20030926025602.GA14592@twcny.rr.com>
On Thu, 25 Sep 2003, Nathanael Nerode wrote:
> Please make it non-case-sensitive, so that [patch] and [Patch] work too.
A variant on this is such notations as [C Patch] and [C++ Patch].
If the patch has already been applied when the mail is sent, there
probably isn't much point in opening a bug for it (given the point of
finding patches that fall through the cracks). So that should have some
notation to indicate it's already been applied (whether in the subject, or
along the lines of the automatic closing notation). Avoiding [PATCH] in
the subject if you maintain the relevant part of the compiler and so have
already applied the patch seems like too much of a kludge.
Arguably it should be possible to mark a patch as being for a particular
bug, [Patch] PR 98765, and then get the discussion attached to the
existing bug report rather than a new one. But this would complicate
automatic closing (an applied patch might or might not *completely* fix
the original bug).
--
Joseph S. Myers
jsm@polyomino.org.uk