From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, tmielczarek@mozilla.com
Subject: Re: patch ping
Date: Tue, 27 Sep 2016 17:50:00 -0000 [thread overview]
Message-ID: <83mvitb5im.fsf@gnu.org> (raw)
In-Reply-To: <87d1jpz40m.fsf@tromey.com> (message from Tom Tromey on Tue, 27 Sep 2016 10:44:25 -0600)
> From: Tom Tromey <tom@tromey.com>
> Cc: gdb-patches@sourceware.org, tmielczarek@mozilla.com
> Date: Tue, 27 Sep 2016 10:44:25 -0600
>
> >>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
>
> Tom> I was talking with a fellow Mozillian today and found out that this
> Tom> patch was never reviewed:
>
> Tom> https://sourceware.org/ml/gdb-patches/2015-05/msg00132.html
>
> Tom> Ping.
>
> Ping.
The documentation part is OK, but please don't use "path" to mean a
file name, GNU coding standards frown on that.
next prev parent reply other threads:[~2016-09-27 17:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 19:27 Tom Tromey
2016-09-27 17:38 ` Tom Tromey
2016-09-27 17:50 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-10 19:34 Patch ping Tom Tromey
2004-05-27 13:07 Paul Brook
2004-05-27 21:20 ` Jason Molenda
2004-05-28 23:37 ` Jim Blandy
2004-04-30 16:27 Ulrich Weigand
2004-04-30 17:33 ` Andrew Cagney
2004-04-30 18:13 ` Ulrich Weigand
2004-04-30 22:19 ` Jim Blandy
2004-04-30 22:51 ` Ulrich Weigand
2004-05-02 20:49 ` Andrew Cagney
2004-05-01 19:48 ` Ulrich Weigand
2004-04-30 22:26 ` Jim Blandy
2004-05-01 15:41 ` Ulrich Weigand
2004-05-02 20:49 ` Jim Blandy
2002-05-13 11:06 Don Howard
2002-05-16 15:54 ` Jim Blandy
2002-01-24 17:25 Tom Tromey
2001-12-07 7:50 Tom Tromey
2001-12-07 8:14 ` Elena Zannoni
2001-12-07 10:00 ` Keith Seitz
2001-12-08 19:57 ` Tom Tromey
2001-12-07 10:46 ` Eli Zaretskii
2001-12-07 11:02 ` 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=83mvitb5im.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tmielczarek@mozilla.com \
--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