From: JWP <elseifthen@gmx.com>
To: Benno Schulenberg <bensberg@justemail.net>, util-linux@vger.kernel.org
Subject: Re: [PATCH 3/3] textual: put option and its description into a single translatable string
Date: Sun, 18 Jan 2015 16:02:49 -0500 [thread overview]
Message-ID: <54BC1F79.1030706@gmx.com> (raw)
In-Reply-To: <1421613631-5732-3-git-send-email-bensberg@justemail.net>
On 01/18/2015 03:40 PM, Benno Schulenberg wrote:
> Also improve the description: notime, notq, and nohost are literals,
> not things to be replaced by something else -- so no angular brackets.
>
> Signed-off-by: Benno Schulenberg <bensberg@justemail.net>
> ---
> misc-utils/logger.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/misc-utils/logger.c b/misc-utils/logger.c
> index 35caf9d..296f7f0 100644
> --- a/misc-utils/logger.c
> +++ b/misc-utils/logger.c
> @@ -525,8 +525,8 @@ static void __attribute__ ((__noreturn__)) usage(FILE *out)
> fputs(_(" -T, --tcp use TCP only\n"), out);
> fputs(_(" -d, --udp use UDP only\n"), out);
> fputs(_(" --rfc3164 use the obsolete BSD syslog protocol\n"), out);
> - fputs(_(" --rfc5424[=<notime,notq,nohost>]\n"), out);
> - fputs(_(" use the syslog protocol (default)\n"), out);
> + fputs(_(" --rfc5424[=<cut>] use the syslog protocol (the default);\n"
> + " <cut> can be notime, or notq, and/or nohost\n"), out);
I have never see that done before, it seems confusing.
Isn't the commonly used term 'snip'?
> fputs(_(" -u, --socket <socket> write to this Unix socket\n"), out);
> #ifdef HAVE_LIBSYSTEMD
> fputs(_(" --journald[=<file>] write journald entry\n"), out);
>
next prev parent reply other threads:[~2015-01-18 21:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 20:40 [PATCH 1/3] ionice: drop the duplicate docstring Benno Schulenberg
2015-01-18 20:40 ` [PATCH 2/3] docs: fix two spellings in man page of logger Benno Schulenberg
2015-01-18 20:40 ` [PATCH 3/3] textual: put option and its description into a single translatable string Benno Schulenberg
2015-01-18 21:02 ` JWP [this message]
2015-01-26 10:28 ` Karel Zak
2015-01-26 10:27 ` [PATCH 1/3] ionice: drop the duplicate docstring Karel Zak
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=54BC1F79.1030706@gmx.com \
--to=elseifthen@gmx.com \
--cc=bensberg@justemail.net \
--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