Re: [PATCH] manual: adjust reference to man-pages following proc(5) split-up

Adhemerval Zanella Netto <[email protected]>
Newsgroups gmane.comp.lib.glibc.alpha
Organization Linaro
Message-ID <[email protected]>

On 29/08/26 16:05, Collin Funk wrote:
> Adhemerval Zanella Netto <[email protected]> writes:
> 
>> On 28/08/26 00:57, Collin Funk wrote:
>>> The reference to MAP_NORESERVE and /proc/sys/vm/overcommit_memory was
>>> moved from proc(5) to proc_sys(5) in man-pages commit bfc1299e7 (proc.5,
>>> proc_sys.5: Split /proc/sys/ from proc(5), 2023-08-15). It was
>>> subsequently moved to proc_sys_vm(5) in man-pages commit
>>> b06cd070f (proc_sys.5, proc_sys_vm.5: Split /proc/sys/vm/ from
>>> proc_sys(5), 2023-09-30).
>>> ---
>>>  manual/llio.texi | 4 ++--
>>>  1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/manual/llio.texi b/manual/llio.texi
>>> index 405174839f..aa8f3b82b5 100644
>>> --- a/manual/llio.texi
>>> +++ b/manual/llio.texi
>>> @@ -1887,8 +1887,8 @@ @node Memory-mapped I/O
>>>  unable to map a page due to lack of resources.
>>>  
>>>  On Linux, this flag's behavior may be overridden by
>>> -@file{/proc/sys/vm/overcommit_memory} as documented in the proc(5) man
>>> -page.
>>> +@file{/proc/sys/vm/overcommit_memory} as documented in the
>>> +proc_sys_vm(5) man page.
>>
>> Maybe add it might be documented in both since we can't be sure which
>> man-pages version has installed.
> 
> Well, I guess there are three pages that it could be in. Not sure if
> proc_sys(5) with that info made it into an actual release.
> 
> My thinking was that only putting the latest one works, since people
> using the latest glibc manual are more likely to have the latest
> man-pages as well.

Fair enough.

LGTM, thanks.

Reviewed-by: Adhemerval Zanella  <[email protected]>

 Or, if they are using the internet they will
> hopefully be looking at the latest glibc manual and man-pages release.
> WDYT?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.