From: Michael Elizabeth Chastain <mec@shout.net>
To: fedor@doc.com, gdb@sources.redhat.com
Subject: Re: Adding patches to 6.0 branch
Date: Sat, 23 Aug 2003 03:13:00 -0000 [thread overview]
Message-ID: <200308230313.h7N3D2P3021453@duracef.shout.net> (raw)
For what it's worth, the patch is already in gdb HEAD
since 2003-08-02, and hasn't drawn any complaints from my test bed.
That certainly doesn't mean "yes", however. I saw the name
'linespec.c' and I laughed out loud.
Michael C
high strung tester
===
2003-08-02 Adam Fedor <fedor@gnu.org>
* linespec.c (is_objc_method_format): New function
(decode_line_1, locate_first_half): Use it.
Fixes PR objc/1298
next reply other threads:[~2003-08-23 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 3:13 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 2:56 Adam Fedor
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=200308230313.h7N3D2P3021453@duracef.shout.net \
--to=mec@shout.net \
--cc=fedor@doc.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