From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@false.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] gdb1250.exp: Handle pending breakpoint in shared library
Date: Thu, 11 Mar 2004 01:55:00 -0000 [thread overview]
Message-ID: <20040311015550.3E82B4B104@berman.michael-chastain.com> (raw)
drow> I'd rather not. You were happy with my last patch to add runto
drow> {allow-pending}, yes? I could just commit that.
I'm happy with your patch, but I haven't seen anything from
Fernando N or Mark S, and those are the only people who can
approve patches in testsuite/lib.
That's why I just capitulated and made gdb1250.exp look like
pending.exp and langs.exp.
Michael C
WARNING: multiple messages have this Message-ID
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: drow@false.org, mec.gnu@mindspring.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] gdb1250.exp: Handle pending breakpoint in shared library
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040311015550.3E82B4B104@berman.michael-chastain.com> (raw)
Message-ID: <20040319000900.Th8MUfrban7fKdaqIwSQioGmE9KmeUgUcuuhF2RICAs@z> (raw)
drow> I'd rather not. You were happy with my last patch to add runto
drow> {allow-pending}, yes? I could just commit that.
I'm happy with your patch, but I haven't seen anything from
Fernando N or Mark S, and those are the only people who can
approve patches in testsuite/lib.
That's why I just capitulated and made gdb1250.exp look like
pending.exp and langs.exp.
Michael C
next reply other threads:[~2004-03-11 1:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 1:55 Michael Elizabeth Chastain [this message]
2004-03-19 0:09 ` Michael Elizabeth Chastain
2004-03-23 23:06 ` Andrew Cagney
2004-03-19 0:09 Michael Elizabeth Chastain
2004-03-11 1:22 ` Michael Elizabeth Chastain
2004-03-11 1:52 ` Daniel Jacobowitz
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-24 18:25 Michael Elizabeth Chastain
2004-03-24 18:42 ` Daniel Jacobowitz
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=20040311015550.3E82B4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@false.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