From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alex Roper <aroper-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Possible typo in madvise(2)
Date: Tue, 01 Apr 2014 20:18:43 +0200 [thread overview]
Message-ID: <533B0303.2000601@gmail.com> (raw)
In-Reply-To: <5334B14B.7070409-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
On 03/28/2014 12:16 AM, Alex Roper wrote:
> Version: Current git repo
>
> The first paragraph of DESCRIPTION states that madvise does not change
> the semantics of an application except in the case of MADV_DONTNEED,
> which I believe should read MADV_DONTFORK.
Alex,
MADV_DONTNEED does change the semantics. But, could you say more
about wht you think MADV_DONTFORK should have been written here
instead? (Perhaps some fix is needed to the page.)
Thanks,
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
next prev parent reply other threads:[~2014-04-01 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 23:16 Possible typo in madvise(2) Alex Roper
[not found] ` <5334B14B.7070409-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2014-04-01 18:18 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <533B0303.2000601-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-01 19:22 ` Alex Roper
[not found] ` <533B120E.1090406-63aXycvo3TyHXe+LvDLADg@public.gmane.org>
2014-04-01 19:25 ` Alex Roper
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=533B0303.2000601@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=aroper-63aXycvo3TyHXe+LvDLADg@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.