From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@redhat.com>,
gdb-patches@sources.redhat.com,
Michael Elizabeth Chastain <mec@shout.net>
Subject: Re: [patch] kfail gdb.c++/annota2.exp annotate-quit
Date: Fri, 20 Dec 2002 10:50:00 -0000 [thread overview]
Message-ID: <ro1hed8ilp5.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20021220171322.GA2610@nevyn.them.org>
On Fri, 20 Dec 2002 12:13:22 -0500, Daniel Jacobowitz <drow@mvista.com> said:
> On Fri, Dec 20, 2002 at 05:04:00PM +0000, Andrew Cagney wrote:
>> Just gdb/NNN is better - identify the bug database and not the category.
> gdb/544 will be fine then.
Okay, then everybody likes gdb/NNN. I'll check that version in.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-12-20 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 7:42 Michael Elizabeth Chastain
2002-12-19 11:01 ` David Carlton
2002-12-19 13:48 ` Daniel Jacobowitz
2002-12-20 9:12 ` Andrew Cagney
2002-12-20 10:09 ` Daniel Jacobowitz
2002-12-20 10:50 ` David Carlton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 20:57 David Carlton
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=ro1hed8ilp5.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--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