From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb@sources.redhat.com, Christopher Faylor <cgf@alum.bu.edu>
Subject: Re: bugzilla
Date: Thu, 08 Jul 2004 15:16:00 -0000 [thread overview]
Message-ID: <D241EDB3-D0F1-11D8-9149-000A95DA505C@dberlin.org> (raw)
In-Reply-To: <40ED6302.3020704@gnu.org>
On Jul 8, 2004, at 11:06 AM, Andrew Cagney wrote:
>> On Jul 8, 2004, at 10:31 AM, Andrew Cagney wrote:
>>> Please discuss :-)
>>>
>>> --
>>>
>>> I've cc'd DanielB and ChrisF who would need to be involved in any
>>> logistical matters.
>>>
>> I've converted the GDB GNATS database before with little or no
>> problems.
>> I can put the results up on www.dberlin.org/bugzilla if you want to
>> see what it looks like
>> The only real problem in conversion is that the bugs will not have
>> the same PR number they used to, though they will be contiguous (IE
>> they will be offset by some number).
>
> Why is a renumbering needed? It's our database can't we do what we
> like? :-)
I was planning on putting you guys in the same bugzilla as the other
sources projects (sources.redhat.com/bugzilla).
Bugs id's are global to a given bugzilla, not local to a given product.
There exist bugs starting with the number one in there already. Thus,
gdb bugs would have to start with the highest number at the time of the
import.
next prev parent reply other threads:[~2004-07-08 15:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 ` Daniel Berlin [this message]
2004-07-08 14:59 ` bugzilla Dave Korn
2004-07-08 15:15 ` bugzilla Daniel Berlin
2004-07-08 18:03 bugzilla Michael Elizabeth Chastain
2004-07-08 19:17 ` bugzilla Daniel Berlin
2004-07-08 18:07 bugzilla Michael Elizabeth Chastain
2004-07-08 19:44 bugzilla Michael Elizabeth Chastain
2007-03-21 8:00 Bugzilla Sascha Radike
2007-03-21 11:11 ` Bugzilla Daniel Jacobowitz
2007-03-21 11:29 ` Bugzilla Sascha Radike
2007-03-21 11:45 ` Bugzilla 'Daniel Jacobowitz'
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
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=D241EDB3-D0F1-11D8-9149-000A95DA505C@dberlin.org \
--to=dberlin@dberlin.org \
--cc=cagney@gnu.org \
--cc=cgf@alum.bu.edu \
--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