From: Michael Kerrisk <mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [patch] document new "e" fopen() flag from glibc-2.7
Date: Mon, 19 Nov 2007 17:17:34 +0100 [thread overview]
Message-ID: <4741B71E.30800@gmail.com> (raw)
In-Reply-To: <200710232000.20800.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Mike Frysinger wrote:
> per the subject, patch attached
> -mike
Hi Mike,
Thanks. Applied for 2.67.
Cheers,
Michael
> ------------------------------------------------------------------------
>
> --- man3/fopen.3.orig 2007-10-23 19:52:39.000000000 -0400
> +++ man3/fopen.3 2007-10-23 19:56:01.000000000 -0400
> @@ -257,6 +257,13 @@
> or subsequent read and write operations,
> thread cancellation points.
> .TP
> +.BR e " (since glibc 2.7)"
> +Open the file with the
> +.B O_CLOEXEC
> +flag. See
> +.BR open (2)
> +for more information.
> +.TP
> .BR m " (since glibc 2.3)"
> Attempt to access the file using
> .BR mmap (2),
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance? Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages/
read the HOWTOHELP file and grep the source files for 'FIXME'.
-
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 parent reply other threads:[~2007-11-19 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710232000.20800.vapier@gentoo.org>
[not found] ` <200710232000.20800.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2007-11-19 16:17 ` Michael Kerrisk [this message]
[not found] ` <4741B71E.30800-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-11-23 17:12 ` [patch] document new "e" fopen() flag from glibc-2.7 Michael Kerrisk
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=4741B71E.30800@gmail.com \
--to=mtk.manpages-gm/ye1e23mwn+bqq9rbeug@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@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