Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gdb@sources.redhat.com
Subject: Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3
Date: Mon, 22 Sep 2003 03:32:00 -0000	[thread overview]
Message-ID: <20030922033248.GA7789@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.56.0309212300231.20144@dberlin.org>

On Sun, Sep 21, 2003 at 11:05:05PM -0400, Daniel Berlin wrote:
> 
> 
> On Sat, 20 Sep 2003, Daniel Jacobowitz wrote:
> 
> > On Fri, Sep 19, 2003 at 07:58:18PM -0400, Christopher Faylor wrote:
> > > On Fri, Sep 19, 2003 at 06:29:09PM -0400, Michael Elizabeth Chastain wrote:
> > > >I think it's good to send the patch to gdb-patches as usual,
> > > >and then mail to gdb-gnats with a URL that points to the patch.
> > > >That means you have to for the patch to show up in the gdb-patches
> > > >archive, but that takes just a few seconds.
> > >
> > > Just as an aside, I'm wondering if it is time to consider switching
> > > to bugzilla.  I think bugzilla handles this issue a little better.
> >
> > I'd say, absolutely.  I've been meaning to ask Daniel B. about setting
> > one up for binutils too.
> 
> binutils is easier than gdb, because binutils has nothing right now.
> Thus, there's nothing to convert :P.
> 
> GDB has GNATS, and in order to keep the bug numbers the same, we'd have
> to set up a new install of bugzilla (since bugzilla bug ids are
> "globally" unique to a given bugzilla instance, rather than unique to a
> given product).

Yeah, at this point I guess we'd prefer to hold on to the PR ids. 
We've documented some of them...

> Does GDB have any different gnats fields than gcc's gnats used to?
> 
> If not, i can run the conversion script on the database, import the data
> into my test database on dberlin.org, and you guys could see what the
> converted db looks like (though i don't have inbound email handling set up
> on my machine).

I don't think it does.  Different things in the category lists et
cetera, of course.  But that's it.  Right now it's:

Reporter, CC, Number, Category, Synopsis, Confidential, Severity,
Priority, Responsible, State, Class, Submitter-Id, Arrival-Date,
Closed-Date, Last-Modified, Originator, Release, Organization,
Environment, Description, File Attachments, How-To-Repeat, Fix,
Release-Note, Unformatted, and the Audit Trail.

Usual caveats about how much some of those are worth.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-09-22  3:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 22:29 Michael Elizabeth Chastain
2003-09-19 23:58 ` Christopher Faylor
2003-09-20  0:04   ` Jim Blandy
2003-09-20  0:19     ` bugzilla (was Re: macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3) Christopher Faylor
2003-09-22  2:55     ` macros/726: Internal GDB errors with current GDB snapshots and -gdwarf2-3 Daniel Berlin
2003-09-20  4:39   ` Daniel Jacobowitz
2003-09-22  3:05     ` Daniel Berlin
2003-09-22  3:32       ` Daniel Jacobowitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-22  3:39 Michael Elizabeth Chastain
     [not found] <200309192212.h8JMCdfS021605@duracef.shout.net>
2003-09-19 22:16 ` Jim Blandy

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=20030922033248.GA7789@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=dberlin@dberlin.org \
    --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