[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e587ddc-99a3-f05a-857d-9d221c0818b1@gmail.com>
Date: Tue, 27 Oct 2020 16:25:04 +0100
From: Alejandro Colomar <colomar.6.4.3@...il.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc: linux-man@...r.kernel.org, libc-alpha@...rceware.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] system_data_types.7: Add 'off_t'
On 2020-10-27 14:47, Michael Kerrisk (man-pages) wrote:
> On 10/27/20 11:23 AM, Alejandro Colomar wrote:
>> Hi Michael,
>>
>> On 2020-10-07 08:53, Michael Kerrisk (man-pages) wrote:
>>> On 10/6/20 12:12 AM, Alejandro Colomar wrote:
>>>> Signed-off-by: Alejandro Colomar <colomar.6.4.3@...il.com>
>>>
>>> Hi Alex,
>>>
>>> Thanks, patch applied. And I trimmed the "See also" a little.
>>> I'd hold off on documenting loff_t and off64_t for the
>>> moment. As you note in another mail, the *lseek* man page
>>> situation is a bit of a mess. I'm not yet sure what to do.
>>
>>
>> I saw a TODO in the page about loff_t.
>> Just wanted to ping you in case you forgot about it (I did).
>
> I didn't forget it exactly. I just don't know that I have the
> inclination to do anything about the messy *llseek* pages.
>
> Thanks,
>
> Michael
>
>
Hi Michael,
I've been reading them to add loff_t and off64_t to sys_data_types.
Now that I've read them (not too deep),
I think that lseek64(3) is good enough,
and maybe we should look for small details
missing there but present on the others,
and merge those to lseek64.3.
And then keep links in the other pages pointing to lseek64.3.
Any thoughts?
Cheers,
A
Powered by blists - more mailing lists