From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: bugzilla vs dejagnu
Date: Mon, 06 Mar 2006 19:31:00 -0000 [thread overview]
Message-ID: <20060306193058.GA11100@nevyn.them.org> (raw)
In-Reply-To: <440C8C46.4000400@redhat.com>
On Mon, Mar 06, 2006 at 02:23:50PM -0500, Andrew Cagney wrote:
> A thread on oversears@ brings up an interesting point.
>
> Where's GDB at with respect to migrating from dejagnu to bugzilla, is
> there still an intent for this to happen?
I assume you mean GNATS to bugzilla?
I still want it to happen. But I don't think anyone had decided what
to do about all the GNATS PR numbers in DejaGNU; we could preserve
them, but only by setting up a separate bugzilla installation, instead
of sharing with the rest of sourceware (and I think sharing the
installation would be in our best interests).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-06 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 19:23 Andrew Cagney
2006-03-06 19:31 ` Daniel Jacobowitz [this message]
2006-03-06 19:59 ` Andreas Schwab
2006-03-06 20:04 ` Daniel Jacobowitz
2006-03-22 22:50 ` bugzilla vs gnats (nee dejagnu :-) Andrew Cagney
2006-03-06 19:35 ` bugzilla vs dejagnu Mark Kettenis
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=20060306193058.GA11100@nevyn.them.org \
--to=drow@false.org \
--cc=cagney@redhat.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