From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb@sources.redhat.com
Subject: Re: gnats -> bugzilla
Date: Mon, 09 Jun 2008 20:39:00 -0000 [thread overview]
Message-ID: <g2k4cf$arl$1@ger.gmane.org> (raw)
In-Reply-To: <je1w36xsgj.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Joel Brobecker <brobecker@adacore.com> writes:
>
>>> If you have any objections, speak up.
>> My only concern is that we have references to bug numbers in our
>> sources as well as inside our testsuite. Are we going to replace
>> these references with the new numbers?
>
> If the bugs are renumbered with a constant offset that is greater than
> the biggest gnats number in use then you can easily identify them and
> map them to the new bz number.
>
There are around 2500 bugs in gnats so maybe <bz number> = 10 * <gnatsno> (the first new PR would, therefore, be something like 25000).
next prev parent reply other threads:[~2008-06-09 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-09 18:28 Tom Tromey
2008-06-09 19:26 ` Stan Shebs
2008-06-09 20:04 ` Joel Brobecker
2008-06-09 20:29 ` Andreas Schwab
2008-06-09 20:39 ` Aleksandar Ristovski [this message]
2008-06-09 20:41 ` Daniel Jacobowitz
2008-06-09 21:31 ` Christopher Faylor
2008-06-10 14:29 ` Jan Kratochvil
2008-06-10 14:48 ` Daniel Jacobowitz
2008-06-10 14:55 ` Jan Kratochvil
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='g2k4cf$arl$1@ger.gmane.org' \
--to=aristovski@qnx.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