From: "Štěpán Němec" <stepnem@smrk.net>
To: util-linux@vger.kernel.org, Benno Schulenberg <bensberg@telfort.nl>
Subject: [PATCH] copyfilerange: (man) fix swapped offsets in command example
Date: Wed, 22 Apr 2026 20:25:03 +0200 [thread overview]
Message-ID: <20260422182503.1111558-1-stepnem@smrk.net> (raw)
In-Reply-To: <bd1c4673-ab3a-4934-a7d1-8113a48c9811@telfort.nl>
Signed-off-by: Štěpán Němec <stepnem@smrk.net>
---
On Wed, 22 Apr 2026 08:17:46 +0200
Benno Schulenberg wrote:
> The convention for the subject line when man pages are affected is:
>
> program: (man) description of change
Interesting.
I did recheck both Documentation/howto-contribute.txt and recent man
page commits before sending the patch, and, having failed to identify
clear guidance, went with the pattern that made more sense to me.
That said, I see now that, had I gone more quantitative about it, I
might have picked the one you prefer :-D
; git log | grep -c '(man): '
21
; git log | grep -c ': (man)'
289
Unfortunately I didn't.
In any case, if the preference is felt strongly enough to require
rerolls just for that, I believe it would make a great addition to
howto-contribute.txt (or at least applying it consistently in the actual
project commit messages; the most recent '(man): ' is from 19. 4.).
Thanks,
Štěpán
misc-utils/copyfilerange.1.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/misc-utils/copyfilerange.1.adoc b/misc-utils/copyfilerange.1.adoc
index 303a1a7b25e2..89b95e9516fa 100644
--- a/misc-utils/copyfilerange.1.adoc
+++ b/misc-utils/copyfilerange.1.adoc
@@ -71,7 +71,7 @@
copyfilerange split-first-mb join ::
-copyfilerange split-remainder join 1M::
+copyfilerange split-remainder join :1M:
....
== SEE ALSO
base-commit: fff8c59c75355d365a69f86719e7bd7818c1daf4
--
2.53.0
next prev parent reply other threads:[~2026-04-22 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 18:05 [PATCH] copyfilerange(man): fix swapped offsets in command example Štěpán Němec
2026-04-21 18:32 ` Dick Marinus
2026-04-22 6:17 ` Benno Schulenberg
2026-04-22 18:25 ` Štěpán Němec [this message]
2026-04-23 9:48 ` [PATCH] copyfilerange: (man) " Benno Schulenberg
2026-04-27 8:14 ` 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=20260422182503.1111558-1-stepnem@smrk.net \
--to=stepnem@smrk.net \
--cc=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