Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: nickrob@snap.net.nz (Nick Roberts)
To: Daniel Jacobowitz <drow@false.org>
Cc: Tom Tromey <tromey@redhat.com>, Doug Evans <dje@google.com>,
		gdb@sourceware.org
Subject: Re: Bugzilla
Date: Sun, 18 Oct 2009 02:27:00 -0000	[thread overview]
Message-ID: <19162.31515.805575.915539@totara.tehura.co.nz> (raw)
In-Reply-To: <20091017234943.GB5612@caradoc.them.org>

 > Sending it to gdb-patches will not make more people pay attention to
 > it, just irritate more people who have to work harder to delete it.

Actually, I think it would initially probably do both.  Messages on
gdb-patches certainly get more attention than bug reports.

 > Those of us with time and patience to deal with the bugzilla traffic
 > already get it from gdb-prs (which is a Bugzilla-only list; you can't
 > post to it, only Bugzilla can; reply to the Bugzilla address).

If bug reports were cc'ed to a mailing list which you already are subscribed
to then presumably you could unsubscribe from gdb-prs so that you still only
receive each bug report once.

 > If we need more people working on the bug system, that's a people
 > problem, not a list configuration problem.

I disagree.  In part it is a configuration problem because the ideal outcome
of a bug report is a patch.  Currently to get attention this requires
cross-posting to gdb-patches which I think is more irritating because
unsubscribing from gdb-prs would result in missing or incomplete bug reports.

In any case, I've unsubscribed from gdb-prs now as I've found it to be a waste
of my time and I won't be submitting any more patches for bugs reported there.

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


  reply	other threads:[~2009-10-18  2:19 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       ` Bugzilla Tom Tromey
2009-10-18  1:03         ` Bugzilla Daniel Jacobowitz
2009-10-18  2:27           ` Nick Roberts [this message]
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=19162.31515.805575.915539@totara.tehura.co.nz \
    --to=nickrob@snap.net.nz \
    --cc=dje@google.com \
    --cc=drow@false.org \
    --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