From: Alejandro Colomar <alx@kernel.org>
To: Stan Ulbrych <stanulbrych@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v1 0/1] man/man3/strptime.3: fix typos
Date: Mon, 6 Apr 2026 00:08:46 +0200 [thread overview]
Message-ID: <adLdJb9OVGD3oD3l@debian> (raw)
In-Reply-To: <CAEMnaZ+paJ5_Dc5FkibQSggqiR9hW7EYLtnn=wmbCz3Cb+iLVw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2257 bytes --]
Hi Stan,
On Mon, Mar 30, 2026 at 10:50:55PM +0200, Stan Ulbrych wrote:
> A little patch to fix a few little issues I noticed in the doc. I've
> never contributed here before so I'm not sure if I'm doing it all
> right, if not, apologies!
>
> From 42228dd6c167dab1d0dd61d2d25b626d0fc2ecfb Mon Sep 17 00:00:00 2001
> From: Stan Ulbrych <stanulbrych@gmail.com>
> Date: Mon, 30 Mar 2026 22:41:23 +0200
> Subject: [PATCH v1 1/1] man/man3/strptime.3: fix typos
Thanks! I've applied the patch.
It was a bit weirdly formatted, but it worked. You may want to look at
the CONTRIBUTING.d/git file and other files under that directory.
Have a lovely ngiht!
Alex
>
> ---
> man/man3/strptime.3 | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/man/man3/strptime.3 b/man/man3/strptime.3
> index b969a2a..979bffe 100644
> --- a/man/man3/strptime.3
> +++ b/man/man3/strptime.3
> @@ -60,7 +60,7 @@ The
> function processes the input string from left
> to right.
> Each of the three possible input elements (whitespace,
> -literal, or format) are handled one after the other.
> +literal, or format) is handled one after the other.
> If the input cannot be matched to the format string, the function stops.
> The remainder of the format and input strings are not processed.
> .P
> @@ -288,7 +288,7 @@ explicitly specified, except that it recomputes the
> .I tm_wday
> and
> .I tm_yday
> -field if any of the year, month, or day elements changed.
> +fields if any of the year, month, or day elements changed.
> .\" .P
> .\" This function is available since libc 4.6.8.
> .\" Linux libc4 and libc5 includes define the prototype unconditionally;
> @@ -319,7 +319,7 @@ the same format characters as for
> (In most cases, the corresponding fields are parsed, but no field in
> .I tm
> is changed.)
> -This leads to
> +This leads to:
> .TP
> .B %F
> Equivalent to
> @@ -364,7 +364,7 @@ and
> .B %P
> is accepted as a synonym for
> .BR %p .
> -Finally
> +Finally:
> .TP
> .B %s
> The number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).
> --
> 2.53.0
>
--
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-04-05 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 20:50 [PATCH v1 0/1] man/man3/strptime.3: fix typos Stan Ulbrych
2026-04-05 22:08 ` Alejandro Colomar [this message]
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=adLdJb9OVGD3oD3l@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=stanulbrych@gmail.com \
/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