From: Gilles Espinasse <g.esp@free.fr>
To: netdev@vger.kernel.org, shemminger@linux-foundation.org
Cc: Gilles Espinasse <g.esp@free.fr>
Subject: [PATCH] iproute2: fix minor typo in comments
Date: Sun, 10 Jul 2011 17:45:37 +0200 [thread overview]
Message-ID: <1310312737-2296-1-git-send-email-g.esp@free.fr> (raw)
Signed-off-by: Gilles Espinasse <g.esp@free.fr>
---
README | 2 +-
README.devel | 2 +-
configure | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/README b/README
index 0ed0372..528b539 100644
--- a/README
+++ b/README
@@ -21,7 +21,7 @@ database routines. Often this is in the db-devel package.
2. make
-The makefile will automatically build a file Config which
+The makefile will automatically build a Config file which
contains whether or not ATM is available, etc.
3. To make documentation, cd to doc/ directory , then
diff --git a/README.devel b/README.devel
index 2022869..9b7d11e 100644
--- a/README.devel
+++ b/README.devel
@@ -1,7 +1,7 @@
Iproute2 development is closely tied to Linux kernel networking
development. Most new features require a kernel and a utility component.
-Please submit both the the Linux networking mailing list
+Please submit both to the Linux networking mailing list
<netdev@vger.kernel.org>
The current source is in the git repository:
diff --git a/configure b/configure
index 600fa96..69797ab 100755
--- a/configure
+++ b/configure
@@ -65,7 +65,7 @@ then
return
fi
-#check if we need dont our internal header ..
+#check if we dont need our internal header ..
cat >/tmp/ipttest.c <<EOF
#include <xtables.h>
char *lib_dir;
--
1.5.6.5
next reply other threads:[~2011-07-10 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 15:45 Gilles Espinasse [this message]
2011-07-11 17:12 ` [PATCH] iproute2: fix minor typo in comments Stephen Hemminger
2011-07-11 19:31 ` Nicolas de Pesloüan
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=1310312737-2296-1-git-send-email-g.esp@free.fr \
--to=g.esp@free.fr \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).