From: Tom Tromey <tromey@redhat.com>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: Bugzilla
Date: Sat, 17 Oct 2009 09:39:00 -0000 [thread overview]
Message-ID: <m3r5t2g78f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <19160.60352.406552.989757@totara.tehura.co.nz> (Nick Roberts's message of "Sat, 17 Oct 2009 10:55:12 +1300")
>>>>> "Nick" == Nick Roberts <nickrob@snap.net.nz> writes:
Nick> I don't think it actually goes to gdb-prs. The Reply-To: header
Nick> is sourceware-bugzilla@sourceware.org while the To: header is
Nick> gdb-prs@sourceware.org. I hit 'reply' in VM which goes to
Nick> bugzilla. If I hit 'followup' which tries to go to both
Nick> addresses, the message gets sent back to me.
Strange, I thought it worked. You can ask overseers to fix it.
The email does go somewhere because the gmane group works and it only
gets gdb bugs -- not bugs from other components in the sourceware
bugzilla.
Nick> In any case, my point is that GDB Bugzilla is a bit of a black
Nick> hole: more goes in than comes out. If reports did go to gdb-prs,
Nick> they would still go unread as presumably no-one is subscribed to
Nick> it. gdb and gdb-patches are the only mailing lists that appear to
Nick> be widely read.
I read all the traffic.
I thought about this and I don't mind where the email goes. I'm going
to read it regardless. I'm skeptical that sending it to gdb-patches
will help the situation much, but I'll set it up if that is what the
rest of the community wants.
Tom
next prev parent reply other threads:[~2009-10-17 1:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 0:56 Bugzilla Nick Roberts
2009-10-15 9:42 ` Bugzilla Doug Evans
2009-10-15 16:07 ` Bugzilla Tom Tromey
2009-10-17 1:05 ` Bugzilla Nick Roberts
2009-10-17 9:39 ` Tom Tromey [this message]
2009-10-18 1:03 ` Bugzilla Daniel Jacobowitz
2009-10-18 2:27 ` Bugzilla Nick Roberts
2009-10-18 2:46 ` Bugzilla Daniel Jacobowitz
2009-10-18 19:41 ` Bugzilla Joel Brobecker
2009-10-20 7:56 ` Bugzilla Nick Roberts
2009-10-20 10:02 ` Bugzilla Joel Brobecker
-- strict thread matches above, loose matches on Subject: below --
2007-03-21 8:00 Bugzilla Sascha Radike
2007-03-21 11:11 ` Bugzilla Daniel Jacobowitz
2007-03-21 11:29 ` Bugzilla Sascha Radike
2007-03-21 11:45 ` Bugzilla 'Daniel Jacobowitz'
2004-07-08 19:44 bugzilla Michael Elizabeth Chastain
2004-07-08 18:07 bugzilla Michael Elizabeth Chastain
2004-07-08 18:03 bugzilla Michael Elizabeth Chastain
2004-07-08 19:17 ` bugzilla Daniel Berlin
2004-07-08 14:31 bugzilla Andrew Cagney
2004-07-08 14:52 ` bugzilla Daniel Berlin
2004-07-08 15:07 ` bugzilla Andrew Cagney
2004-07-08 15:11 ` bugzilla Daniel Jacobowitz
2004-07-08 15:17 ` bugzilla Daniel Berlin
2004-07-08 15:16 ` bugzilla Daniel Berlin
2004-07-08 14:59 ` bugzilla Dave Korn
2004-07-08 15:15 ` bugzilla Daniel Berlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r5t2g78f.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox