From: Jan Synacek <jsynacek@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: netdev@vger.kernel.org, Jan Synacek <jsynacek@redhat.com>
Subject: [PATCH] ping doc: Fix typo.
Date: Fri, 18 Jan 2013 12:21:36 +0100 [thread overview]
Message-ID: <1358508096-19915-1-git-send-email-jsynacek@redhat.com> (raw)
Signed-off-by: Jan Synacek <jsynacek@redhat.com>
---
doc/ping.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/ping.sgml b/doc/ping.sgml
index 4e0e65f..eec92a2 100644
--- a/doc/ping.sgml
+++ b/doc/ping.sgml
@@ -600,7 +600,7 @@ Many Hosts and Gateways ignore the RECORD_ROUTE option.
<listitem><para>
The maximum IP header length is too small for options like
RECORD_ROUTE to be completely useful.
-There's not much that that can be done about this, however.
+There's not much that can be done about this, however.
</para></listitem>
<listitem><para>
Flood pinging is not recommended in general, and flood pinging the
--
1.8.0.2
next reply other threads:[~2013-01-18 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 11:21 Jan Synacek [this message]
2013-01-18 18:20 ` [PATCH] ping doc: Fix typo YOSHIFUJI Hideaki
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=1358508096-19915-1-git-send-email-jsynacek@redhat.com \
--to=jsynacek@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).