From: Alexander Holler <holler@ahsoftware.de>
To: linux-kernel@vger.kernel.org
Cc: linux-doc@vger.kernel.org, Rob Landley <rob@landley.net>,
Alexander Holler <holler@ahsoftware.de>
Subject: [PATCH] Documentation: correct typo in dynamic-debug-howto.txt (echo -c -> echo -n)
Date: Wed, 1 Jan 2014 12:54:54 +0100 [thread overview]
Message-ID: <1388577294-5587-1-git-send-email-holler@ahsoftware.de> (raw)
In-Reply-To: <52BD71D7.9060709@landley.net>
As nobody could answer what the parameter -c for echo should be, I assume
it's a typo. Normally I don't care much about those, but this one might make
people search for the meaning of the parameter -c.
Signed-off-by: Alexander Holler <holler@ahsoftware.de>
---
Documentation/dynamic-debug-howto.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/dynamic-debug-howto.txt b/Documentation/dynamic-debug-howto.txt
index 1bbdcfc..abb7dfe 100644
--- a/Documentation/dynamic-debug-howto.txt
+++ b/Documentation/dynamic-debug-howto.txt
@@ -91,9 +91,9 @@ Command Language Reference
At the lexical level, a command comprises a sequence of words separated
by spaces or tabs. So these are all equivalent:
-nullarbor:~ # echo -c 'file svcsock.c line 1603 +p' >
+nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
<debugfs>/dynamic_debug/control
-nullarbor:~ # echo -c ' file svcsock.c line 1603 +p ' >
+nullarbor:~ # echo -n ' file svcsock.c line 1603 +p ' >
<debugfs>/dynamic_debug/control
nullarbor:~ # echo -n 'file svcsock.c line 1603 +p' >
<debugfs>/dynamic_debug/control
--
1.8.1.4
prev parent reply other threads:[~2014-01-01 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 17:38 What does echo -c do (as found in dynamic-debug-howto.txt) Alexander Holler
2013-12-27 12:25 ` Rob Landley
2014-01-01 11:54 ` Alexander Holler [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=1388577294-5587-1-git-send-email-holler@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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