From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Gdb List <gdb@sources.redhat.com>
Subject: Re: Gnats
Date: Tue, 11 Mar 2008 00:52:00 -0000 [thread overview]
Message-ID: <m3iqzuta6s.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080310233548.GQ11769@adacore.com> (Joel Brobecker's message of "Mon\, 10 Mar 2008 16\:35\:48 -0700")
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> In related news, who thinks we should bite the bullet and migrate to
>> the sourceware bugzilla installation?
Joel> Perhaps I don't use the current bugs database enough to see the
Joel> problems that come with it.
The gnats web interface has some annoying problems, that's for sure.
Also, some simple operations cannot be done. For instance, you can't
easily mark a bug as a duplicate.
Joel> But I think whether the switch will be useful or not
Joel> depends on how much resources we would have available to monitor the
Joel> contents of the database. Right now, it feel like very little effort is
Joel> spent using the current bugs database, and so a switch wouldn't bring
Joel> much benefit.
Today I went through 1/2 to 2/3 of the bugs, looking for dead stuff.
There was less than I thought, but still a bit. Also there are a few
relatively straightforward patches that have been sitting there
unviewed -- not to mention bigger, useful stuff like the 'try/except'
patch.
I agree that changing bug systems will only have a minimal effect, if
any, on this sort of thing. So, consider this a plea for a bit more
attention to the bug database from maintainers :)
Tom
next prev parent reply other threads:[~2008-03-11 0:37 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 ` Tom Tromey [this message]
2008-03-11 21:20 ` Gnats Daniel Berlin
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=m3iqzuta6s.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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