From: Ulrich Drepper <drepper@redhat.com>
To: Nicholas Miell <nmiell@comcast.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, torvalds@linux-foundation.org
Subject: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Date: Thu, 31 May 2007 11:32:15 -0700 [thread overview]
Message-ID: <465F14AF.3020908@redhat.com> (raw)
In-Reply-To: <1180635728.3104.3.camel@entropy>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Nicholas Miell wrote:
> O_CLOSEONEXEC, perhaps?
Then nobody would know this is equivalent to FD_CLOEXEC. I think the
name I propose is fine.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGXxSv2ijCOnn/RHQRAhELAJ9/7pTQeZShV6NDfEx+iVSfD5g02gCeM/y+
E0GvuEg2EBtOmDdI5MEzOG0=
=W6hQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-05-31 18:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 18:09 [PATCH] Introduce O_CLOEXEC (take >2) Ulrich Drepper
2007-05-31 18:22 ` Nicholas Miell
2007-05-31 18:32 ` Ulrich Drepper [this message]
2007-05-31 18:35 ` Davide Libenzi
2007-05-31 18:42 ` Ulrich Drepper
2007-05-31 18:46 ` Davide Libenzi
2007-05-31 18:53 ` Ulrich Drepper
2007-05-31 19:02 ` Jakub Jelinek
2007-05-31 19:17 ` Davide Libenzi
2007-05-31 19:50 ` Ulrich Drepper
2007-05-31 20:23 ` Davide Libenzi
2007-05-31 19:59 ` Linus Torvalds
2007-05-31 23:20 ` Andrew Morton
2007-06-01 1:05 ` Stephen Rothwell
2007-06-01 1:38 ` Stephen Rothwell
2007-06-01 3:07 ` [parisc-linux] " Kyle McMartin
2007-06-01 3:07 ` Kyle McMartin
2007-06-01 19:17 ` Byron Stanoszek
2007-06-01 22:55 ` Kyle McMartin
2007-06-01 22:55 ` [parisc-linux] " Kyle McMartin
2007-06-01 19:17 ` Byron Stanoszek
2007-06-10 2:29 ` dean gaudet
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=465F14AF.3020908@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nmiell@comcast.net \
--cc=torvalds@linux-foundation.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.