From: Tom Tromey <tromey@redhat.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: add pr numbers
Date: Sun, 14 Apr 2002 08:22:00 -0000 [thread overview]
Message-ID: <87wuvacnev.fsf@creche.redhat.com> (raw)
In-Reply-To: Daniel Berlin's message of "14 Apr 2002 03:12:21 -0400"
>>>>> "Dan" == Daniel Berlin <dberlin@dberlin.org> writes:
Dan> However, this *is* actually going to be annoying in the initial
Dan> import, since it means that if they share the same bugzilla
Dan> system (which only makes sense), i'll have to remap gdb's bug
Dan> numbers to a new range (IE add 10000 to them. There are almost
Dan> exactly 7000 gcc bug reports, and not going to be 3000 more
Dan> before we switch)
When we imported the libgcj Gnats database into the gcc database, we
had to renumber. We just added a comment to every PR: "Previously PR
libgcj/OLD-NUMBER". In the few situations where I've needed to look
up a PR by its old number, this has let me do it easily.
Tom
next prev parent reply other threads:[~2002-04-14 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-13 23:41 Michael Elizabeth Chastain
2002-04-14 0:12 ` Daniel Berlin
2002-04-14 6:31 ` Andrew Cagney
2002-04-14 8:22 ` Tom Tromey [this message]
2002-04-20 18:45 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2002-04-22 22:19 Michael Elizabeth Chastain
2002-04-22 22:17 Michael Elizabeth Chastain
2002-04-21 20:29 Michael Elizabeth Chastain
2002-04-14 1:02 Michael Elizabeth Chastain
2002-04-13 15:06 Michael Elizabeth Chastain
2002-04-13 17:45 ` Daniel Berlin
2002-04-12 18:24 Michael Elizabeth Chastain
2002-04-12 15:27 Michael Elizabeth Chastain
2002-04-12 17:08 ` Kevin Buettner
2002-04-12 17:20 ` Daniel Jacobowitz
2002-04-13 14:58 ` Andrew Cagney
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=87wuvacnev.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=ac131313@cygnus.com \
--cc=dberlin@dberlin.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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