Re: [PATCH] Introduce O_CLOEXEC (take >2)

-----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-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH] Introduce O_CLOEXEC (take >2)
  - From: Ulrich Drepper <[email protected]>
- Re: [PATCH] Introduce O_CLOEXEC (take >2)
  - From: Nicholas Miell <[email protected]>

Prev by Date: Re: 2.6.22-rc3-mm1
Next by Date: Re: + loop-preallocate-eight-loop-devices.patch added to -mm tree
Previous by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Next by thread: Re: [PATCH] Introduce O_CLOEXEC (take >2)
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]