From: Phil Muldoon <pmuldoon@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] News. Document gdb.Write stream keyword.
Date: Tue, 22 Mar 2011 10:58:00 -0000 [thread overview]
Message-ID: <m3fwqfjwpy.fsf@redhat.com> (raw)
In-Reply-To: <E1Q1cdE-0000pH-B4@fencepost.gnu.org> (Eli Zaretskii's message of "Mon, 21 Mar 2011 06:46:40 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Phil Muldoon <pmuldoon@redhat.com>
>> Reply-to: pmuldoon@redhat.com
>> Date: Mon, 21 Mar 2011 10:09:10 +0000
>>
>>
>> I forgot to include this with the patch from last week. I'm not sure it
>> qualifies as newsworthy, but it does note an addition to the API.
>> Shall I add it?
>
> Unless others object, please do. Thanks.
I've committed this, thanks.
Cheers,
Phil
prev parent reply other threads:[~2011-03-22 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:45 Phil Muldoon
2011-03-21 13:36 ` Eli Zaretskii
2011-03-22 10:58 ` Phil Muldoon [this message]
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=m3fwqfjwpy.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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