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: Future of gccbug



On Nov 7, 2003, at 3:01 PM, gnat-dev@buzco.nyct.net wrote:


On 03-11-07 14:28:53, Daniel Berlin wrote:

[ BIG snip}

| Um, can you guys please notify me when things about Bugzilla annoy you?
| Even if I don't do something immediately, I do keep track of input and
| whatnot when making changes to it, and determining what way things
| should work.


=== End quoted text ===

OK, you asked for it! :)

Having mail coming from bugzilla, requiring replies to bugzilla, on
+any+ other list makes replying properly a pain. A couple of days ago I
sent a bunch of stuff to gcc-bugs thinking it would get to bugzilla

There's no easy way to do this with our current list software, AFAIK.


If we could make it ignore replies to gcc-bugs that aren't from gcc-bugzilla (ignore as in not let them go to the list), and redirect them to gcc-bugzilla, everything would be happy, methinks.



and
didn't realize it until hours later. End result was that the stuff got
to bugzilla out-of order and late and showed up on gcc-bugs +twice+,
once for the original submissions and again for the re-submissions to
bugzilla.

I find the mail and WWW interfaces +both+ useful, but it would be nicer
if bugzilla mail +visibly+ came from bugzilla.

It does. It's got a from of gcc-bugzilla@gcc.gnu.org

People want to know who made the changes, that's why the "quoted name" is the person's email address.

There's some "proper" way to do this with "Sender" and "Envelope-From", but no email client i know of handles them right.

All told, if someone who understands the list software can work with us, ..


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