public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Ganimedes Colomar <gacoan.linux@gmail.com>,
	linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH 2/2] Various pages: Normalize NOTES about non-existing glibc wrappers
Date: Tue, 29 Dec 2020 21:53:47 +0100	[thread overview]
Message-ID: <842d4263-0fd5-ea70-bac0-1f4abd405c20@gmail.com> (raw)
In-Reply-To: <CAKgNAkgiZiycjW3r=-LTzV0g1CyboYokqcgQbe9hYRT6MWjUTg@mail.gmail.com>

Hi Michael,

Please, see a comment below.

Thanks,

Alex

On 12/29/20 9:32 PM, Michael Kerrisk (man-pages) wrote:
> Hi Alex, Ganimedes,
> 
> Again, in the subject line, s/
> 
> non-existing/nonexistent/
> 
> [...]
> 
>> --- a/man2/getdents.2
>> +++ b/man2/getdents.2
>> @@ -211,13 +211,13 @@ SVr4.
>>  Library support for
>>  .BR getdents64 ()
>>  was added in glibc 2.30;
>> -there is no glibc wrapper for
>> -.BR getdents ().
>> -Calling
>> +Glibc does not provide a wrapper for
>> +.BR getdents ();
>> +call
> 
> s/call/calling/

See below

> 
>>  .BR getdents ()
>>  (or
>>  .BR getdents64 ()
>> -on earlier glibc versions) requires the use of
>> +on earlier glibc versions) using

The new version is 'Call XXX using syscall(2).'.

>>  .BR syscall (2).
>>  In that case you will need to define the
>>  .I linux_dirent
> 
> [...]
> 
> Again, the only reason I'm not making these patches and making the
> minor fixes is in case you find some other pages that might be added
> to the patch. Let me know.
> 
> Thanks,
> 
> Michael
> 

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

  reply	other threads:[~2020-12-29 20:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 14:38 [PATCH 0/2] Normalize notes about missing glibc wrappers Alejandro Colomar
2020-12-29 14:39 ` [PATCH 1/2] Various pages: Normalize SYNOPSIS notes about non-existing " Alejandro Colomar
2020-12-29 14:49   ` Alejandro Colomar (man-pages)
2020-12-29 20:27   ` Michael Kerrisk (man-pages)
2020-12-29 20:51     ` Alejandro Colomar (man-pages)
2020-12-30  9:37       ` Michael Kerrisk (man-pages)
2020-12-29 14:39 ` [PATCH 2/2] Various pages: Normalize NOTES " Alejandro Colomar
2020-12-29 20:32   ` Michael Kerrisk (man-pages)
2020-12-29 20:53     ` Alejandro Colomar (man-pages) [this message]
2020-12-30  9:38       ` Michael Kerrisk (man-pages)
2020-12-30 12:52         ` Alejandro Colomar (man-pages)
2020-12-30 13:23           ` Michael Kerrisk (man-pages)
2020-12-30 15:20             ` [PATCH v2 0/2] Normalize notes about missing " Alejandro Colomar
2020-12-30 15:20             ` [PATCH v2 1/2] Various pages: Normalize SYNOPSIS notes about nonexistent " Alejandro Colomar
2020-12-30 19:20               ` Michael Kerrisk (man-pages)
2020-12-30 15:20             ` [PATCH v2 2/2] Various pages: Normalize NOTES " Alejandro Colomar
2020-12-30 16:07               ` Michael Kerrisk (man-pages)
2020-12-30 21:01                 ` Alejandro Colomar (man-pages)
2020-12-29 20:19 ` [PATCH 0/2] Normalize notes about missing " Michael Kerrisk (man-pages)
2020-12-29 20:45   ` Alejandro Colomar (man-pages)
2020-12-30  9:30     ` 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=842d4263-0fd5-ea70-bac0-1f4abd405c20@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=gacoan.linux@gmail.com \
    --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