From: Alejandro Colomar <alx@kernel.org>
To: seth.i.mcdonald@gmail.com
Cc: Seth McDonald <sethmcmail@pm.me>, linux-man@vger.kernel.org
Subject: Re: [PATCH v1 3/4] man/man2/utime.2: SYNOPSIS: ffix
Date: Wed, 31 Dec 2025 14:45:20 +0100 [thread overview]
Message-ID: <aVUods3LbVTwIhCa@devuan> (raw)
In-Reply-To: <fad6d60041620c94de4aed504bfffdf28b22cf46.1767072049.git.sethmcmail@pm.me>
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
Hi Seth,
On Tue, Dec 30, 2025 at 04:42:02PM +1000, seth.i.mcdonald@gmail.com wrote:
> From: Seth McDonald <sethmcmail@pm.me>
>
> Increments the indentation of the times parameter in the utimes(2)
> prototype by one space.
>
> Signed-off-by: Seth McDonald <sethmcmail@pm.me>
> ---
> man/man2/utime.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man/man2/utime.2 b/man/man2/utime.2
> index 94307a5b90..e044f15b06 100644
> --- a/man/man2/utime.2
> +++ b/man/man2/utime.2
> @@ -18,7 +18,7 @@ .SH SYNOPSIS
> .B #include <sys/time.h>
> .P
> .BI "int utimes(const char *" path ,
> -.BI " const struct timeval " times "[_Nullable 2]);"
> +.BI " const struct timeval " times "[_Nullable 2]);"
The current formatting is intended, and documented in man-pages(7):
In the SYNOPSIS, a long function prototype may need to be
continued over to the next line. The continuation line is
indented according to the following rules:
[...]
(2) But, where multiple functions in the SYNOPSIS require
continuation lines, and the function names have dif‐
ferent lengths, then align all continuation lines to
start in the same column. This provides a nicer ren‐
dering in PDF output (because the SYNOPSIS uses a
variable width font where spaces render narrower than
most characters). As an example:
int getopt(int argc, char * const argv[],
const char *optstring);
int getopt_long(int argc, char * const argv[],
const char *optstring,
const struct option *longopts, int *longindex);
Have a lovely day!
Alex
P.S.: These patches work correctly. :)
> .fi
> .SH DESCRIPTION
> .B Note:
> --
> 2.47.3
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-31 13:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 6:41 [PATCH v1 0/4] Miscellaneous fixes seth.i.mcdonald
2025-12-30 6:42 ` [PATCH v1 1/4] man/man2/syscall.2: Add HISTORY section seth.i.mcdonald
2025-12-31 13:46 ` Alejandro Colomar
2025-12-30 6:42 ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix seth.i.mcdonald
2025-12-30 6:59 ` Collin Funk
2025-12-30 7:18 ` Seth McDonald
2025-12-30 7:27 ` G. Branden Robinson
2025-12-30 7:40 ` Collin Funk
2025-12-30 7:53 ` G. Branden Robinson
2025-12-30 11:34 ` Alejandro Colomar
2025-12-30 7:22 ` Is 2.11BSD < 4BSD? It depends. (was: [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix) G. Branden Robinson
2025-12-30 7:35 ` Is 2.11BSD < 4BSD? It depends Collin Funk
2025-12-31 13:46 ` [PATCH v1 2/4] sys/man2/sysctl.2: HISTORY: wfix Alejandro Colomar
2025-12-30 6:42 ` [PATCH v1 3/4] man/man2/utime.2: SYNOPSIS: ffix seth.i.mcdonald
2025-12-31 13:45 ` Alejandro Colomar [this message]
2025-12-30 6:42 ` [PATCH v1 4/4] man/man2const/F_GETSIG.2const: HISTORY: tfix seth.i.mcdonald
2025-12-31 13:47 ` Alejandro Colomar
2025-12-31 13:48 ` [PATCH v1 0/4] Miscellaneous fixes Alejandro Colomar
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=aVUods3LbVTwIhCa@devuan \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=seth.i.mcdonald@gmail.com \
--cc=sethmcmail@pm.me \
/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;
as well as URLs for NNTP newsgroup(s).