Util-Linux package development
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Cc: "Petr Písař" <petr.pisar@atlas.cz>
Subject: [PATCH 2/4] textual: fix a mistruncated message, and fix a typo
Date: Sun,  6 Apr 2025 17:21:45 +0200	[thread overview]
Message-ID: <20250406152147.9225-2-bensberg@telfort.nl> (raw)
In-Reply-To: <20250406152147.9225-1-bensberg@telfort.nl>

The phrase "in human-readable form" was chosen rather than
"in human-readable format" because it's shorter and lets
the line fit *just* within 80 columns.

Reported-by: Petr Písař <petr.pisar@atlas.cz>
Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
 sys-utils/lsipc.c   | 2 +-
 sys-utils/setpriv.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-utils/lsipc.c b/sys-utils/lsipc.c
index 7b041790b..d292ab96c 100644
--- a/sys-utils/lsipc.c
+++ b/sys-utils/lsipc.c
@@ -338,7 +338,7 @@ static void __attribute__((__noreturn__)) usage(void)
 	fputs(_("     --noheadings         don't print headings\n"), out);
 	fputs(_("     --notruncate         don't truncate output\n"), out);
 	fputs(_("     --time-format=<type> display dates in short, full or iso format\n"), out);
-	fputs(_(" -b, --bytes              print SIZE in bytes rather\n"), out);
+	fputs(_(" -b, --bytes              print SIZE in bytes rather than in human-readable form\n"), out);
 	fputs(_(" -c, --creator            show creator and owner\n"), out);
 	fputs(_(" -e, --export             display in an export-able output format\n"), out);
 	fputs(_(" -J, --json               use the JSON output format\n"), out);
diff --git a/sys-utils/setpriv.c b/sys-utils/setpriv.c
index daa3ab366..433db6031 100644
--- a/sys-utils/setpriv.c
+++ b/sys-utils/setpriv.c
@@ -1025,7 +1025,7 @@ int main(int argc, char **argv)
 		case SECCOMP_FILTER:
 			if (opts.seccomp_filter)
 				errx(EXIT_FAILURE,
-				     _("duplicate --secccomp-filter option"));
+				     _("duplicate --seccomp-filter option"));
 			opts.seccomp_filter = optarg;
 			break;
 		case RESET_ENV:
-- 
2.48.1


  reply	other threads:[~2025-04-06 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-06 15:21 [PATCH 1/4] hwclock: remove two comments about parameters that no longer exist Benno Schulenberg
2025-04-06 15:21 ` Benno Schulenberg [this message]
2025-04-06 15:21 ` [PATCH 3/4] zramctl: restore normal description indentations in the usage text Benno Schulenberg
2025-04-06 15:21 ` [PATCH 4/4] zramctl: (man) mention the required arguments for -p and -r Benno Schulenberg
2025-04-08 11:44 ` [PATCH 1/4] hwclock: remove two comments about parameters that no longer exist 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=20250406152147.9225-2-bensberg@telfort.nl \
    --to=bensberg@telfort.nl \
    --cc=petr.pisar@atlas.cz \
    --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