From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Cc: David Anes <david.anes@suse.com>
Subject: [PATCH 06/10] renice: in usage text, condense the oververbose description of option -n
Date: Thu, 17 Apr 2025 11:48:20 +0200 [thread overview]
Message-ID: <20250417094825.20870-6-bensberg@telfort.nl> (raw)
In-Reply-To: <20250417094825.20870-1-bensberg@telfort.nl>
The --help text should be concise: it serves only as a reminder of how
things work. When a more wordy explanation is needed, there is always
the man page (as every --help text says at the end).
CC: David Anes <david.anes@suse.com>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
sys-utils/renice.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/sys-utils/renice.c b/sys-utils/renice.c
index eac104db3..7872e8fbb 100644
--- a/sys-utils/renice.c
+++ b/sys-utils/renice.c
@@ -70,10 +70,8 @@ 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"
- " 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(_(" -n <num> specify the 'absolute' nice value,\n"
+ " but 'relative' when POSIXLY_CORRECT is set\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-04-17 9:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 9:48 [PATCH 01/10] bits: (man) normalize the markup and improve some layout Benno Schulenberg
2025-04-17 9:48 ` [PATCH 02/10] last: (man) correct the descriptions of --present and --since Benno Schulenberg
2025-04-17 9:48 ` [PATCH 03/10] last: (man) reduce an inflated table to sane proportions Benno Schulenberg
2025-04-17 9:48 ` [PATCH 04/10] rtcwake: " Benno Schulenberg
2025-04-17 9:48 ` [PATCH 05/10] terminal-colors.d: (man) reduce two tables to succinct lists Benno Schulenberg
2025-04-17 9:48 ` Benno Schulenberg [this message]
2025-04-17 9:48 ` [PATCH 07/10] renice: (man) reword several things, to be clearer, and improve some markup Benno Schulenberg
2025-04-17 9:48 ` [PATCH 08/10] lscpu: (man) don't refer to a missing section, and improve some wordings Benno Schulenberg
2025-04-17 9:48 ` [PATCH 09/10] docs: correct misspellings of "may be" and mistaken uses of "overwritten" Benno Schulenberg
2025-04-17 9:48 ` [PATCH 10/10] docs: correct mistaken uses of "overwrite" to say "override" instead Benno Schulenberg
2025-04-17 9:58 ` [PATCH 01/10] bits: (man) normalize the markup and improve some layout Robin Jarry
2025-04-24 9:57 ` 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=20250417094825.20870-6-bensberg@telfort.nl \
--to=bensberg@telfort.nl \
--cc=david.anes@suse.com \
--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