From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch Pings
Date: Tue, 12 Jul 2016 18:49:00 -0000 [thread overview]
Message-ID: <83wpkqae1b.fsf@gnu.org> (raw)
In-Reply-To: <87vb0aogo9.fsf@tromey.com> (message from Tom Tromey on Tue, 12 Jul 2016 12:27:34 -0600)
> From: Tom Tromey <tom@tromey.com>
> CC: Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 12 Jul 2016 12:27:34 -0600
>
> Eli, CCing you for this patch, which needs a doc review:
>
> https://sourceware.org/ml/gdb-patches/2016-06/msg00395.html
>
>
> Previous ping was here:
>
> https://sourceware.org/ml/gdb-patches/2016-06/msg00407.html
Sorry about that. The documentation part of that patch is OK.
Thanks.
next prev parent reply other threads:[~2016-07-12 18:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 18:27 Tom Tromey
2016-07-12 18:49 ` Eli Zaretskii [this message]
2016-07-12 18:56 ` Eli Zaretskii
2016-07-13 16:29 ` Tom Tromey
2016-07-14 16:54 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2017-08-11 20:10 patch pings Tom Tromey
2016-10-28 13:34 Patch pings Maciej W. Rozycki
2016-06-24 20:52 patch pings Tom Tromey
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=83wpkqae1b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).