public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, linux-man@vger.kernel.org
Subject: Re: [PATCH] strftime.3: document how %z and %Z are calculated
Date: Wed, 8 Mar 2023 22:19:51 +0100	[thread overview]
Message-ID: <11a95096-6b54-5e48-e6ff-adeafebddc64@gmail.com> (raw)
In-Reply-To: <20230308205344.745801-1-eggert@cs.ucla.edu>


[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]

Hi Paul,

Thanks for resending inline!  :)

Another thing: please CC or TO me; otherwise I might miss the email.
See the ./CONTRIBUTING file in the repo for more details if necessary.


On 3/8/23 21:53, Paul Eggert wrote:

Would you please add some links in the commit message
to the discussion you had about this?

> ---
>  man3/strftime.3 | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/man3/strftime.3 b/man3/strftime.3
> index 57b2a38aa..90248d0b4 100644
> --- a/man3/strftime.3
> +++ b/man3/strftime.3
> @@ -417,6 +417,8 @@ The
>  or
>  .I \-hhmm
>  numeric timezone (that is, the hour and minute offset from UTC). (SU)

My question was about this "(SU)" marker.  Should we move it to after
the new sentence maybe?  (Same for "(TZ)" below.)

Cheers,

Alex

> +(Calculated from
> +.IR tm_gmtoff .)
>  .TP
>  .B %Z
>  The timezone name or abbreviation.
> @@ -427,6 +429,8 @@ The timezone name or abbreviation.
>  The date and time in
>  .BR date (1)
>  format. (TZ)
> +(Calculated from
> +.IR tm_zone .)
>  (Not supported in glibc2.)
>  .TP
>  .B %%

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-03-08 21:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 20:53 [PATCH] strftime.3: document how %z and %Z are calculated Paul Eggert
2023-03-08 21:19 ` 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=11a95096-6b54-5e48-e6ff-adeafebddc64@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=linux-man@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