From: Alejandro Colomar <alx@kernel.org>
To: Zijun Zhao <zijunzhao@google.com>
Cc: linux-man@vger.kernel.org, enh <enh@google.com>
Subject: Re: [PATCH] Fix the man page
Date: Fri, 28 Jul 2023 22:48:10 +0200 [thread overview]
Message-ID: <9b26cd45-08e1-8905-4b8a-dfa65d654b99@kernel.org> (raw)
In-Reply-To: <CAELULbd+_kOKdJcKuTS8XqbcFyeZB6Qsi8J_YAe6WuO_+n=26A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2643 bytes --]
On 2023-07-27 20:33, Zijun Zhao wrote:
> Hi Alejandro,
> Sorry for the late reply! Thank you for your help! Yes, all comments
> are very clear, understandable and helpful! This is the new patch.
> Thank you for reviewing! Also, thank Elliott for helping! Hope this
> patch is qualified!
> Best,
> Zijun
Heh, I replied to the wrong email. Thanks for the patch; I applied it
(I applied this one, even if I replied to the other one).
Cheers,
Alex
>
>
> On Sat, Jul 15, 2023 at 9:13 AM Alejandro Colomar <alx@kernel.org> wrote:
>>
>> Hi Zijun,
>>
>> On 2023-07-12 01:48, Zijun Zhao wrote:
>>> Hi Alejandro,
>>> Sorry for the late reply!
>>
>> No problem :-)
>>
>>> I made some changes(make the subject more
>>> formal, add a blank line, respect the80-column right margin and use -u
>>> to when doing git format-patch) and attached the patch below.
>>
>> Thanks!
>>
>>> But I am
>>> a bit confused about semantic newlines. I think I already start on a
>>> new line and use clause breaks to split long sentences? Do I
>>> misunderstand something? Thank you!
>>
>> Here's your patch, modified to use semantic newlines:
>>
>> +The kernel accepts null for both time and timezone.
>> +The timezone argument is ignored by glibc and musl,
>> +and not passed to/from the kernel.
>> +Android's bionic passes the timezone argument to/from the kernel,
>> +but Android does not update the kernel timezone
>> +based on the device timezone in Settings,
>> +so the kernel's timezone is typically UTC.
>>
>> Does it make sense now?
>>
>> I'll also comment a few things about the patch:
>>
>>> +The kernel accepts null for both time and timezone.
>>
>> We should use the 'tv' and 'tz' identifiers. We should also use NULL.
>> I suggest:
>>
>> The kernel accepts NULL for both
>> .I tv
>> and
>> .IR tz .
>>
>>> +The timezone argument is ignored by glibc and musl,
>>> +and not passed to/from the kernel.
>>> +Android's bionic passes the timezone argument to/from the kernel,
>>
>> Could you give an example of why bionic differs from glibc and musl,
>> and why it can be useful. It is mostly curiosity, but it might be
>> useful to have it documented in the commit message.
>>
>>> +but Android does not update the kernel timezone
>>> +based on the device timezone in Settings,
>>> +so the kernel's timezone is typically UTC.
>>
>> Cheers,
>> Alex
>>
>> --
>> <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-07-28 20:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 23:20 [PATCH] Fix the man page Zijun Zhao
2023-05-18 23:27 ` Zijun Zhao
2023-05-18 23:30 ` enh
2023-05-19 8:03 ` Alejandro Colomar
2023-05-19 22:21 ` enh
2023-05-19 22:41 ` Alejandro Colomar
2023-06-05 19:03 ` Zijun Zhao
2023-06-16 21:10 ` Zijun Zhao
[not found] ` <CAJgzZoqS-QJWX87P5B1LQxCktm9BAVfVVBwBxV87RhmQg0fsdg@mail.gmail.com>
2023-06-16 22:26 ` enh
2023-07-08 18:02 ` Alejandro Colomar
2023-07-08 18:37 ` Alejandro Colomar
2023-07-11 23:48 ` Zijun Zhao
2023-07-15 16:13 ` Alejandro Colomar
2023-07-27 18:33 ` Zijun Zhao
2023-07-28 20:48 ` Alejandro Colomar [this message]
2023-07-28 20:58 ` Zijun Zhao
2023-06-20 18:21 ` Zijun Zhao
2023-07-28 20:41 ` 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=9b26cd45-08e1-8905-4b8a-dfa65d654b99@kernel.org \
--to=alx@kernel.org \
--cc=enh@google.com \
--cc=linux-man@vger.kernel.org \
--cc=zijunzhao@google.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