From: Joel Brobecker <brobecker@adacore.com>
To: Gdb List <gdb@sources.redhat.com>
Subject: Re: Gnats
Date: Tue, 11 Mar 2008 00:05:00 -0000 [thread overview]
Message-ID: <20080310233548.GQ11769@adacore.com> (raw)
In-Reply-To: <20080310191331.GA12690@caradoc.them.org>
> 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.
--
Joel
next prev parent reply other threads:[~2008-03-10 23:36 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 ` Joel Brobecker [this message]
2008-03-11 0:52 ` Gnats Tom Tromey
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=20080310233548.GQ11769@adacore.com \
--to=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