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

On Fri, Oct 16, 2009 at 07:05:36PM -0600, Tom Tromey wrote:
> 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.

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.
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 we need more people working on the bug system, that's a people
problem, not a list configuration problem.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-10-17 23:49 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         ` Daniel Jacobowitz [this message]
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=20091017234943.GB5612@caradoc.them.org \
    --to=drow@false.org \
    --cc=dje@google.com \
    --cc=gdb@sourceware.org \
    --cc=nickrob@snap.net.nz \
    --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