From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Subject: [PATCH 11/14] renice: put text that belongs together into a single translatable message
Date: Sun, 9 Feb 2025 09:23:27 +0100 [thread overview]
Message-ID: <20250209082330.4235-11-bensberg@telfort.nl> (raw)
In-Reply-To: <20250209082330.4235-1-bensberg@telfort.nl>
Also, use semicolons and no periods in an option description.
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
sys-utils/renice.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/sys-utils/renice.c b/sys-utils/renice.c
index 419cef46d..eac104db3 100644
--- a/sys-utils/renice.c
+++ b/sys-utils/renice.c
@@ -70,10 +70,10 @@ static void __attribute__((__noreturn__)) usage(void)
fputs(_("Alter the priority of running processes.\n"), out);
fputs(USAGE_OPTIONS, out);
- fputs(_(" -n <num> specify the nice value\n"), out);
- fputs(_(" If POSIXLY_CORRECT flag is set in environment\n"), out);
- fputs(_(" then the priority is 'relative' to current\n"), out);
- fputs(_(" process priority. Otherwise it is 'absolute'.\n"), out);
+ fputs(_(" -n <num> specify the nice value;\n"
+ " if POSIXLY_CORRECT flag is set in environment,\n"
+ " then the priority is 'relative' to current\n"
+ " process priority; otherwise it is 'absolute'\n"), out);
fputs(_(" --priority <num> specify the 'absolute' nice value\n"), out);
fputs(_(" --relative <num> specify the 'relative' nice value\n"), out);
fputs(_(" -p, --pid interpret arguments as process ID (default)\n"), out);
--
2.48.1
next prev parent reply other threads:[~2025-02-09 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-09 8:23 [PATCH 01/14] setpriv: make message for failing PR_GET_PDEATHSIG the same as the other Benno Schulenberg
2025-02-09 8:23 ` [PATCH 02/14] unshare: don't use "=" before a required option argument Benno Schulenberg
2025-02-09 8:23 ` [PATCH 03/14] unshare: use single asterisks around long options, double around values Benno Schulenberg
2025-02-09 8:23 ` [PATCH 04/14] textual: remove other inconsistent uses of "=" before option argument Benno Schulenberg
2025-02-09 8:23 ` [PATCH 05/14] textual: consistently mark "=" as literal before an optional argument Benno Schulenberg
2025-02-09 8:23 ` [PATCH 06/14] mount: properly mark the arguments of the 'ro' and 'rw' extended options Benno Schulenberg
2025-02-09 8:23 ` [PATCH 07/14] unshare: don't mark "|" and ":" as part of the placeholders Benno Schulenberg
2025-02-09 8:23 ` [PATCH 08/14] textual: give seven error messages the same form as two others Benno Schulenberg
2025-02-09 8:23 ` [PATCH 09/14] blkpr: grammarize the description of the tool and its options Benno Schulenberg
2025-02-09 8:23 ` [PATCH 10/14] blkzone: correct the wording of an error message, from ioctl to function Benno Schulenberg
2025-02-10 11:28 ` Karel Zak
2025-02-09 8:23 ` Benno Schulenberg [this message]
2025-02-09 8:23 ` [PATCH 12/14] man pages: use the same verb for --version as for --help, like in usages Benno Schulenberg
2025-02-09 8:23 ` [PATCH 13/14] usage: mention also the missing KiB and MiB as permissible suffixes Benno Schulenberg
2025-02-09 8:23 ` [PATCH 14/14] zramctl: improve grammar in usage and don't gettextize list of algorithms Benno Schulenberg
2025-02-12 10:01 ` [PATCH 01/14] setpriv: make message for failing PR_GET_PDEATHSIG the same as the other 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=20250209082330.4235-11-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--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