From: Daniel Jacobowitz <drow@false.org>
To: Sascha Radike <sascha@pasalacqua.de>
Cc: gdb@sourceware.org
Subject: Re: Bugzilla
Date: Wed, 21 Mar 2007 11:11:00 -0000 [thread overview]
Message-ID: <20070321111126.GA27561@caradoc.them.org> (raw)
In-Reply-To: <000101c76b8e$e9a57010$02b2a8c0@insanenotebook>
On Wed, Mar 21, 2007 at 08:59:47AM +0100, Sascha Radike wrote:
> Hi,
>
> is there any date planned for switching to bugzilla? I think this would be
> very helpful as bugzilla is just much more comfortable than the current bug
> tracker.
>
> I don't know if it is possible to migrate from gnatsweb to bugzilla, but I
> guess a simple solution would be to mark the gnatsweb as 'old' and setup a
> new, fresh bugzilla. Maybe it is possible to send out a message to all users
> who raised a bug and ask them to add their bug to bugzilla if the bug still
> exists. Bugs being addressed for the next release could also be moved to
> bugzilla.
>
> I think it would be an improvement to the GDB project.
We meant to do it ages ago. I was actually thinking about it again
last night...
We can automatically migrate bugs to bugzilla. My understanding is
that the only reasonable way to do it is to add ourselves to the
sourceware.org bugzilla instance, which will renumber all the PRs.
But we should be able to keep the old gnats around for read access
somehow.
Do other people think the time has come to switch over? If so I can
make time to get it done, but otherwise I have plenty of other
projects ;-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-21 11:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 8:00 Bugzilla Sascha Radike
2007-03-21 11:11 ` Daniel Jacobowitz [this message]
2007-03-21 11:29 ` Bugzilla Sascha Radike
2007-03-21 11:45 ` Bugzilla 'Daniel Jacobowitz'
-- strict thread matches above, loose matches on Subject: below --
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 ` 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
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=20070321111126.GA27561@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=sascha@pasalacqua.de \
/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