From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Yaarit <yaarit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Bug report - stat 2 - Description section
Date: Wed, 05 Aug 2015 21:00:15 +0200 [thread overview]
Message-ID: <55C25D3F.5010400@gmail.com> (raw)
In-Reply-To: <CAP6jbrRRJkdjc3jt3t3sjTFkicmq1Jjrizij5Bw-QUrD=GG6pA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08/05/2015 03:30 PM, Yaarit wrote:
> Hello there,
>
> I believe there is a small mistake in the *Description* section of these
> man pages:
> http://man7.org/linux/man-pages/man2/stat.2.html
> http://man7.org/linux/man-pages/man2/fstatat.2.html
> http://man7.org/linux/man-pages/man2/lstat.2.html
> http://man7.org/linux/man-pages/man2/stat64.2.html
> http://man7.org/linux/man-pages/man2/lstat64.2.html
> http://man7.org/linux/man-pages/man2/fstat64.2.html
>
>
> When referring to the functions' second argument (*struct stat ***buf*) in
> the Description, it reads:
>
> These functions return information about a file, in the buffer pointed
> to by *stat*.
>
> instead of:
>
> These functions return information about a file, in the buffer pointed
> to by *buf*.
Thanks, Yaarit. Fixed.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
parent reply other threads:[~2015-08-05 19:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAP6jbrRRJkdjc3jt3t3sjTFkicmq1Jjrizij5Bw-QUrD=GG6pA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
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=55C25D3F.5010400@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=yaarit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).