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: gccbug reports?



On Jun 14, 2004, at 11:30 PM, Steve Kargl wrote:


On Mon, Jun 14, 2004 at 11:21:51PM -0400, Andrew Pinski wrote:
I use the email interface because I can attach patches to a bug report.
If you go to bugzilla and create a new bug report, there is no way
to *attach* (i.e., preserve tabs) a patch.

That is not true because you can attach the patch via the normal file attachment, in fact there is a spot to say that this file is a patch.


I certainly don't see anything like you describe in my browser when I go to http://gcc.gnu.org/bugzilla/enter_bug.cgi.


It's not part of enter_bug (this is an oft-requested feature, a bug exists for it on bugzilla.mozilla.org filed against bugzilla. it's being discussed for bugzilla 2.18) right now.
It is part of the interface once the bug is created.
create bug -> click to go to created bug (or does it bring you to the new bug automatically. I always forget) -> click "create attachment"



The email-interface was an afterthought (and except for the "appending to already existing bugs script"), is an incredibly huge kludge that merges the mess of gnatsweb, and the mess of gnats2bz.pl, into a mess that handles gccbug reports.
The fact that it works at all is a miracle, and the fact that it handles attachments is because i had added code to gnats2bz.pl to do so, and it just happened to work right when it processes regular emails too.
:)



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