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


Daniel Berlin <dberlin@dberlin.org> writes:

| On Nov 7, 2003, at 2:34 PM, Gabriel Dos Reis wrote:
| 
| > Daniel Berlin <dberlin@dberlin.org> writes:
| >
| > | 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.
| >
| > I'm wondering whether having bugzilla send mails to gcc-bugzilla only
| Huh?
| gcc-bugzilla isn't a mailing list, it's an email alias that runs the
| incoming email handler when you email it.
| No outgoing emails are ever sent *to* gcc-bugzilla.

Hmm, then something is wrong somewhere.  Everything that is entered in
bugzilla gets posted to me with a To: gcc-bugs and Reply-To: gcc-bugzilla.
It happens that a wide-reply sends mails to both addresses and things
get duplicated.  My suggestion is to have a separate list for
gcc-bugzilla traffic.

| > -- no Cc: gcc-bugs -- wouldn't improve readability.
| >
| > | IE user input is important to me.
| >
| > hmm, I mostly use Emacs/Gnus in a tty -- I don't know if you care :-/
| >
| 
| I care about all my users, even the poor misguided ones :P

my mails are on a different server than my laptop and I see nothing
misguided in keeping them in one place.  I see nothing misguided in
using a terminal to run an editor that reads news, mails, edit codes,
makes coffee...  

-- Gaby


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