From: Alejandro Colomar <colomar.6.4.3@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/4] system_data_types.7: wfix
Date: Fri, 18 Sep 2020 23:32:23 +0200 [thread overview]
Message-ID: <cff41318-06f2-af10-747c-2a0ed1e70e84@gmail.com> (raw)
In-Reply-To: <4d201c89-8c47-8487-3672-b9af39c1bf2d@gmail.com>
Hello Michael,
On 2020-09-18 22:27, Michael Kerrisk (man-pages) wrote:
>> -Describes times in seconds and microseconds.
>> +Describes elapsed time in seconds and microseconds.
>> .IP
>> Conforming to: POSIX.1-2001 and later.
>> .IP
>
> I don;t think this patch is correct. At the least, it needs
> more explanation. As far as I can see, 'timespec' is not just
> about elapsed time. It really is just time, expressed as secs +
> nanosecs. For example, see utimensat(2), which set file timestamps
> with nanosec precision.
I took that wording from timeval.3bsd. But I think you're correct.
>
> For the moment, I'm not applying this (and I hope not doing so
> doesn't break any following patch).
That's fine. It shouldn't break anything.
>
> Thanks,
>
> Michael
>
Cheers,
Alex
next prev parent reply other threads:[~2020-09-18 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 12:45 [PATCH 0/4] Document regoff_t (and a few minor patches) Alejandro Colomar
2020-09-18 12:45 ` [PATCH 1/4] system_data_types.7: wfix Alejandro Colomar
2020-09-18 20:27 ` Michael Kerrisk (man-pages)
2020-09-18 21:32 ` Alejandro Colomar [this message]
2020-09-18 12:45 ` [PATCH 2/4] system_data_types.7: Document regoff_t Alejandro Colomar
2020-09-18 20:30 ` Michael Kerrisk (man-pages)
2020-09-18 12:45 ` [PATCH 3/4] regoff_t.3: New link to new documented type in system_data_types(7) Alejandro Colomar
2020-09-18 20:31 ` Michael Kerrisk (man-pages)
2020-09-18 12:45 ` [PATCH 4/4] system_data_types.7: srcfix: Add FIXME notes Alejandro Colomar
2020-09-18 20:32 ` Michael Kerrisk (man-pages)
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=cff41318-06f2-af10-747c-2a0ed1e70e84@gmail.com \
--to=colomar.6.4.3@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--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