This is the mail archive of the
mailing list for the GCC project.
Re: Starting to track patches through bugzilla
- From: Daniel Berlin <dberlin at dberlin dot org>
- To: Hans-Peter Nilsson <hp at bitrange dot com>
- Cc: gcc-patches at gcc dot gnu dot org, <gcc at gcc dot gnu dot org>
- Date: Sat, 27 Sep 2003 17:03:16 -0400
- Subject: Re: Starting to track patches through bugzilla
- References: <Pine.BSF.firstname.lastname@example.org>
On Sep 27, 2003, at 4:35 PM, Hans-Peter Nilsson wrote:
On Sat, 27 Sep 2003, Daniel Berlin wrote:
On Sep 27, 2003, at 4:13 PM, Hans-Peter Nilsson wrote:
Anyway, why not have bugzilla look at *all messages* to
gcc-patches that don't reference another instead of telling
people how to mark their patches to please bugzilla?
Because i'm starting simple?
Right now I'm not going to try to match all text in the message and
the text in the <possibly compressed> attachments against a regular
expression to detect diffs.
That's not what I suggested. Like matching Subject with a tag,
you just match the absence of In-Reply-To in the header before
But we don't *look* closer (IE the only validation we currently perform
is the matching of [PATCH]).
Not all new threads on gcc-patches contain patches, so until i'm
looking for diffs in mails, doing what you suggest would track more
than just patches, it would track random started discussions without
For email to gcc-patches, that is. You don't
look at email going elsewhere, I presume. False positives, you