Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: tromey@redhat.com
Cc: Doug Evans <dje@google.com>, gdb@sourceware.org
Subject: Re: Bugzilla
Date: Sat, 17 Oct 2009 01:05:00 -0000	[thread overview]
Message-ID: <19160.60352.406552.989757@totara.tehura.co.nz> (raw)
In-Reply-To: <m38wfc3aql.fsf@fleche.redhat.com>

Tom Tromey writes:
 > >>>>> "Doug" == Doug Evans <dje@google.com> writes:
 > 
 > Doug> Hi.  The mailing list web page says gdb-prs@sourceware.org is the list
 > Doug> to use, though there's still a problem as the archives only have one
 > Doug> message from 2004.  Heh.
 > Doug> http://sourceware.org/gdb/mailing-lists/
 > 
 > Yeah, something is screwy with the archive.
 > I haven't investigated it.
 > 
 > Doug> I like the idea of a separate list.
 > 
 > The mail actually does go to gdb-prs.
 > Or you can read it in gmane as gmane.comp.gdb.bugs.discuss.

I don't think it actually goes to gdb-prs.  The Reply-To: header is
sourceware-bugzilla@sourceware.org while the To: header is
gdb-prs@sourceware.org.  I hit 'reply' in VM which goes to bugzilla.  If I hit
'followup' which tries to go to both addresses, the message gets sent back to
me.  This would explain why there is only one message in gdb-prs.

In any case, my point is that GDB Bugzilla is a bit of a black hole: more
goes in than comes out.  If reports did go to gdb-prs, they would still go
unread as presumably no-one is subscribed to it. gdb and gdb-patches are
the only mailing lists that appear to be widely read.

-- 
Nick                                           http://users.snap.net.nz/~nickrob


  reply	other threads:[~2009-10-16 21:55 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     ` Nick Roberts [this message]
2009-10-17  9:39       ` Bugzilla Tom Tromey
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=19160.60352.406552.989757@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=tromey@redhat.com \
    /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