From: Alex Colomar <alx.manpages@gmail.com>
To: Almaz Mingaleev <mingaleev@google.com>
Cc: enh <enh@google.com>,
mtk.manpages@gmail.com, linux-man@vger.kernel.org,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: %z and %Z in strftime man page require clarification
Date: Sat, 25 Feb 2023 01:40:16 +0100 [thread overview]
Message-ID: <7803b627-9fbb-44be-bd41-04611c43ee2e@gmail.com> (raw)
In-Reply-To: <CAJ0cOr_4QjacU1miDEZGjgkLtVaLk8f-KHVsB_J=c=-C+DTXBA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2914 bytes --]
Hi Almaz,
On 2/24/23 17:40, Almaz Mingaleev wrote:
> I've started a new thread, but can't see it in the mailing list archives.
> Please see the patch attached.
Thanks!
Could you please send the patch inline (if you use git-format-patch(1),
that would be --no-attach (or --inline, but I prefer --no-attach)), so I
can quote reply on it?
If you fear that your mailer will do harmful stuff, please send it both
attached and inline.
Cheers,
Alex
>
>
> On Wed, 15 Feb 2023 at 17:34, Almaz Mingaleev <mingaleev@google.com> wrote:
>>
>> Hi Alex,
>>
>> Patch is somewhat ready, I will send it once a teammate reviews it.
>> Should be ready by tomorrow.
>>
>> I'd definitely appreciate if Paul checks it too :)
>>
>>
>> On Wed, 15 Feb 2023 at 17:21, Alejandro Colomar <alx.manpages@gmail.com> wrote:
>>>
>>> Hi Elliott, Almaz,
>>>
>>> On 2/13/23 17:31, enh wrote:
>>>> (given how complex a topic this is -- based on the discussion on the
>>>> tz mailing list -- you might want to send a specific suggestion in the
>>>> form of a patch...)
>>>
>>> Thanks, I agree. This is too complex, and it would be nice to
>>> see a more specific suggestion in the form of a patch.
>>> I CCed Paul, in case he can help.
>>>
>>> Cheers,
>>>
>>> Alex
>>>
>>>>
>>>> On Mon, Feb 13, 2023 at 1:15 AM Almaz Mingaleev <mingaleev@google.com> wrote:
>>>>>
>>>>> Friendly ping.
>>>>>
>>>>>
>>>>> On Thu, 28 Jul 2022 at 09:16, Almaz Mingaleev <mingaleev@google.com> wrote:
>>>>>>
>>>>>> Hi Michael,
>>>>>> Current strftime specification in C language standard is not accurate.
>>>>>> It tells that tm_isdst is enough to find out time zone's offset. But
>>>>>> that's not true, for example Europe/Lisbon has changed [0] its
>>>>>> standard offset from 00:00 to 01:00 and back to 00:00, so an exact
>>>>>> date is needed to answer that.
>>>>>>
>>>>>> To get correct answer with the current glibc tm struct should either
>>>>>> come from localtime or there should be a mktime call prior to
>>>>>> strftime. You can find a repro example and discussion here [1]. Paul
>>>>>> Eggert has proposed a fix to C standard [2].
>>>>>>
>>>>>> Should man pages reflect that i.e. mention that there should be
>>>>>> localtime/mktime calls for %z and %Z?
>>>>>>
>>>>>> Thanks,
>>>>>> Almaz
>>>>>>
>>>>>> P.S. I am resending the email. My previous attempt was bounced back as
>>>>>> it wasn't TEXT/PLAIN.
>>>>>>
>>>>>> [0] https://github.com/eggert/tz/blob/a249a0c64b2f87a24c7f1aab43056fb597c95b96/europe#L2400
>>>>>> [1] https://mm.icann.org/pipermail/tz/2022-July/031668.html
>>>>>> [2] https://mm.icann.org/pipermail/tz/2022-July/031674.html
>>>
>>> --
>>> <http://www.alejandro-colomar.es/>
>>> GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-02-25 0:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 8:16 %z and %Z in strftime man page require clarification Almaz Mingaleev
2023-02-13 9:15 ` Almaz Mingaleev
2023-02-13 16:31 ` enh
2023-02-15 17:21 ` Alejandro Colomar
2023-02-15 17:34 ` Almaz Mingaleev
2023-02-24 16:40 ` Almaz Mingaleev
2023-02-25 0:40 ` Alex Colomar [this message]
[not found] ` <CAJ0cOr99WV6fbdPj3t7QHG4QH0oHAPZb-8sJWYJ0SPMBBYc_Og@mail.gmail.com>
2023-02-25 1:11 ` Paul Eggert
2023-02-27 8:52 ` Almaz Mingaleev
2023-02-27 20:43 ` Paul Eggert
2023-02-28 14:32 ` Almaz Mingaleev
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=7803b627-9fbb-44be-bd41-04611c43ee2e@gmail.com \
--to=alx.manpages@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=enh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=mingaleev@google.com \
--cc=mtk.manpages@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