Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: "Gdb List" <gdb@sources.redhat.com>
Subject: Re: Gnats
Date: Tue, 11 Mar 2008 21:20:00 -0000	[thread overview]
Message-ID: <4aca3dc20803111402m1ea7ec8bld2962cf17161d5bd@mail.gmail.com> (raw)
In-Reply-To: <20080310233548.GQ11769@adacore.com>

On Mon, Mar 10, 2008 at 6:35 PM, Joel Brobecker <brobecker@adacore.com> wrote:
> > In related news, who thinks we should bite the bullet and migrate to
>  > the sourceware bugzilla installation?
>
>  Perhaps I don't use the current bugs database enough to see the problems
>  that come with it. But I think whether the switch will be useful or not
>  depends on how much resources we would have available to monitor the
>  contents of the database. Right now, it feel like very little effort is
>  spent using the current bugs database, and so a switch wouldn't bring
>  much benefit.

FWIW, the exact same thing was true with GCC when it was using GNATS.
No GCC dev's used it or paid attention, etc.
Within 2 months of the switch, there were even dedicated people
monitoring the database that came out of the woodwork (andrew pinski,
for example), and developers were using it.
It turns out if you have tools that suck, people don't use them :)


  parent reply	other threads:[~2008-03-11 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 19:13 Gnats Tom Tromey
2008-03-10 19:32 ` Gnats Daniel Jacobowitz
2008-03-10 23:36   ` Gnats Tom Tromey
2008-03-11  0:05   ` Gnats Joel Brobecker
2008-03-11  0:52     ` Gnats Tom Tromey
2008-03-11 21:20     ` Daniel Berlin [this message]
2008-03-11 11:52   ` Gnats Andrew STUBBS
2008-03-11 15:06     ` Gnats Daniel Jacobowitz

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=4aca3dc20803111402m1ea7ec8bld2962cf17161d5bd@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=brobecker@adacore.com \
    --cc=gdb@sources.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