From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb@sources.redhat.com
Subject: Re: gdb 5.3 versus gdb HEAD%200302015
Date: Mon, 17 Feb 2003 16:44:00 -0000 [thread overview]
Message-ID: <200302171644.h1HGi3p12340@duracef.shout.net> (raw)
> Nope, there was no PR, just a patch when I noticed it. Besides, didn't
> we want to only use PRs in the GDB database? This would be an
> external/closed.
Works for me. Heck, I think I argued for that position anyways!
Unfortunately gdb_mi_test does not have a multi-armed form so
I have to use a blunt setup_kfail.
I'll go file an external/closed PR for this and then point the
test case at it.
Michael C
next reply other threads:[~2003-02-17 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 16:44 Michael Elizabeth Chastain [this message]
2003-02-17 16:50 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-02-17 17:08 Michael Elizabeth Chastain
2003-02-17 17:13 ` David Carlton
2003-02-17 17:02 Michael Elizabeth Chastain
2003-02-17 16:32 Michael Elizabeth Chastain
2003-02-17 16:35 ` Daniel Jacobowitz
2003-02-17 15:32 Michael Elizabeth Chastain
2003-02-17 15:39 ` Daniel Jacobowitz
2003-02-17 17:03 ` David Carlton
2003-02-18 14:59 ` Michal Ludvig
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=200302171644.h1HGi3p12340@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--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