From: Sami Kerola <kerolasa@iki.fi>
To: util-linux@vger.kernel.org
Cc: kerolasa@iki.fi
Subject: [PATCH 2/3] script: error in usage() output
Date: Sun, 1 Apr 2012 20:19:31 +0200 [thread overview]
Message-ID: <1333304372-25944-3-git-send-email-kerolasa@iki.fi> (raw)
In-Reply-To: <1333304372-25944-1-git-send-email-kerolasa@iki.fi>
Error originates to commit 3ff526391fb5c6b33418dc9cfec31c2ff9b4792e
which is bit more than year, and part or releases v2.20 & v2.21.
Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---
term-utils/script.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/term-utils/script.c b/term-utils/script.c
index 0d891b8..effedac 100644
--- a/term-utils/script.c
+++ b/term-utils/script.c
@@ -133,7 +133,7 @@ usage(FILE *out)
fputs(_("\nOptions:\n"), out);
fputs(_(" -a, --append append the output\n"
" -c, --command <command> run command rather than interactive shell\n"
- " -r, --return return exit code of the child process\n"
+ " -e, --return return exit code of the child process\n"
" -f, --flush run flush after each write\n"
" --force use output file even when it is a link\n"
" -q, --quiet be quiet\n"
--
1.7.9.5
next prev parent reply other threads:[~2012-04-01 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 19:27 [pull] chkdupexe, a bug, version numbers and bashisms Sami Kerola
2012-03-30 15:04 ` Karel Zak
2012-04-01 18:19 ` Sami Kerola
2012-04-01 18:19 ` [PATCH 1/3] tests: hwclock: locate ntpdate by using path Sami Kerola
2012-04-02 11:22 ` Karel Zak
2012-04-01 18:19 ` Sami Kerola [this message]
2012-04-02 11:27 ` [PATCH 2/3] script: error in usage() output Karel Zak
2012-04-01 18:19 ` [PATCH 3/3] chkdupexe: reimplement command in C Sami Kerola
2012-04-02 11:10 ` Karel Zak
2012-04-02 11:53 ` Sami Kerola
2012-04-02 12:12 ` Karel Zak
2012-04-04 10:24 ` Karel Zak
2012-04-02 12:22 ` Pádraig Brady
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=1333304372-25944-3-git-send-email-kerolasa@iki.fi \
--to=kerolasa@iki.fi \
--cc=util-linux@vger.kernel.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