From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: jimb@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: gdb.base/charset.exp: tighten regexp for ^C
Date: Thu, 17 Jun 2004 21:34:00 -0000 [thread overview]
Message-ID: <20040617213405.5EB004B104@berman.michael-chastain.com> (raw)
jimb> Ping? I reported the systems on which I tested it in a followup
jimb> message.
jimb>
jimb> http://sources.redhat.com/ml/gdb-patches/2004-06/msg00064.html
And I replied in
http://sources.redhat.com/ml/gdb-patches/2004-06/msg00091.html
I'm still using this ancient 'mailx' mailer which doesn't thread
messages. I apologize for that. :(
Anyways, I hereby approve this patch.
Michael C
> 2004-06-03 Jim Blandy <jimb@redhat.com>
>
> * gdb.base/charset.exp: Only send a control-C if we see a new
> prompt and incomplete command.
next reply other threads:[~2004-06-17 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 21:34 Michael Elizabeth Chastain [this message]
2004-06-17 22:15 ` Jim Blandy
2004-06-18 23:13 ` Jim Blandy
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 5:31 Jim Blandy
2004-06-04 21:55 ` Jim Blandy
2004-06-17 21:11 ` 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=20040617213405.5EB004B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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