This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH, HURD]: null pathnames shall return ENOENT

From: Roland McGrath <roland at redhat dot com>
To: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
Cc: libc-alpha at sources dot redhat dot com
Date: Mon, 21 Sep 2009 11:01:44 -0700 (PDT)
Subject: Re: [PATCH, HURD]: null pathnames shall return ENOENT
References: <20090918214309.GQ5485@const.famille.thibault.fr><20090918215702.680FA9A6@magilla.sf.frob.com><20090921175500.GD6140@const.famille.thibault.fr>

> Ok, should it rather be kept as an internal glibc flag, or exposed
> through bits/fcntl.h?  Would O_REPARENT be ok?

No, I meant a bool argument to the internal function.  If we want to add a
user feature for this, that would take more consideration.  (I don't think
we do.)

Follow-Ups:
- Re: [PATCH, HURD]: null pathnames shall return ENOENT
  - From: Samuel Thibault

References:
- Re: [PATCH, HURD]: null pathnames shall return ENOENT
  - From: Roland McGrath
- Re: [PATCH, HURD]: null pathnames shall return ENOENT
  - From: Samuel Thibault

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]