This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Future of gccbug
On 03-11-07 15:09:49, Daniel Berlin wrote:
| On Nov 7, 2003, at 3:01 PM, gnat-dev@buzco.nyct.net wrote:
| > On 03-11-07 14:28:53, Daniel Berlin wrote:
| > 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.
I dunno, +this+ list does just what I said. The +original+ msg-id,
in-reply=to, and references are passed along nicely.
[snip (mostly other stuff in my original mail)]
| > 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
Ah, but the "To: gcc-bugs" is what my mail reader (the Mutt) detects and
displays in the addressee column. Even if it didn't, the anti-spam
munging of the originator's name would make it too long to fit
conveniently on the screen.
| People want to know who made the changes, that's why the "quoted name"
| is the person's email address.
Ah, there is another pain! That stuff is (to me) just garbage that is
not visible until I open the message, and is then duplicated in the
body. Further, to reply to the mail cleanly, I must then +manually+
remove that junk from the "To: " of the reply. A pain, as I said.
[snip]
=== End quoted text ===
== Buz :)
--
Buz Cory of BuzCo Systems -- New York NY USA http://BuzCo dot nyct dot net
<gnat-dev at BuzCo dot nyct dot net> (Buz as GNAT Programmer)
write to <helpdesk at BuzCo dot nyct dot net> for FREE help with:
Installing/Configuring Linux
Getting started with the Ada Programming Language dot
Friends don't let friends do DOS; Linux to the rescue!
Ada 95 is here! Why use an archaic, bug-prone language?