Junio C Hamano <gits...@pobox.com> wrote:
> Our codepaths themselves generally do not care about O_CLOEXEC, so
> giving a racy emulation of it is not worth the effort, making the
> later half of the above an overkill.
> Perhaps the three lines to
> define O_CLOEXEC to 0 on older UNIX might be sufficient.
I'd be more comfortable keeping the EINVAL check that got
snipped in your reply. O_CLOEXEC can be defined to non-zero in
new userspace headers, but an older kernel chokes on it with
I've seen this failure in the past with chroots.
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html