Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: dberlin@dberlin.org
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/local.exp: add pr numbers
Date: Sun, 14 Apr 2002 01:02:00 -0000	[thread overview]
Message-ID: <200204140802.g3E82j832166@duracef.shout.net> (raw)

Daniel Berlin writes:

  1. Bugzilla supports multiple products by default, in a single database.
  (Each product can itself, have multiple components, as well)
  2. Bug ids are unique within a given bugzilla database.

Ah.  Ok.  So this covers the case that I care about the most, which is
referring to gcc bugs.  As far as I know, gcc (broadly speaking, the
whole "gnu compiler collection") are the only Free Software compilers
supported by gdb.  Although maybe my knowledge is limited?

> However, this *is* actually going to be annoying in the initial import,
> since it means that if they share the same bugzilla system (which only
> makes sense), i'll have to remap gdb's bug numbers to a new range (IE
> add 10000 to them. There are almost exactly 7000 gcc bug reports, and
> not going to be 3000 more before we switch)

So gnats bug #277 is going to become bugzilla bug #10277, for instance?

Michael C


             reply	other threads:[~2002-04-14  8:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-14  1:02 Michael Elizabeth Chastain [this message]
  -- 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-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
2002-04-20 18:45 ` Andrew Cagney
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=200204140802.g3E82j832166@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@cygnus.com \
    --cc=dberlin@dberlin.org \
    --cc=gdb-patches@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