This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Starting to track patches through bugzilla


It could happen that someone starts a mail with an RFC or
bug report - and then later someone replies to that thread
with a PATCH proposal - shouldn't that be prosessed as a
patch then?

Perhaps it is better to scan the body for attachments, and
detect the existance of a patch based on typical 'diff'-like
output.

Also, if I understand you right - this describes how mails
to gcc-patches@ will be filtered/detected and processed/included
on GNATs.  But the other way around is also needed imho:
When someone creates an attachment on GNAT for an existing
PR he can mark that attachment as a patch - if he does that,
then I think a mail should go out to patches@, including
the patch (or when the patch is very large - with just a
link to it).

Just ideas,

-- 
Carlo Wood <carlo@alinoe.com>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]