From: Florian Weimer <fw@deneb.enyo.de>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] manual: Add Descriptor-Relative Access section
Date: Tue, 12 May 2020 09:19:02 +0200 [thread overview]
Message-ID: <87mu6dzkm1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <CALxWeYq5BPUG2XBCCT-gnYEsWnN22S6-zYmH=qUtmmwZNWMNng@mail.gmail.com> (Michael Kerrisk's message of "Tue, 12 May 2020 08:02:52 +0200")
* Michael Kerrisk:
> One more thought...
>
>> +@itemize @bullet
>> +@item
>> +It can be a file descriptor referring to a directory. Such a descriptor
>> +can be created explicitly using the @code{open} function, with or
>> +without the @code{O_DIRECTORY} flag.
>
> Is it worth mentioning O_PATH here?
Do you mean like this?
+It can be a file descriptor referring to a directory. Such a descriptor
+can be created explicitly using the @code{open} function, with or
+without the @code{O_DIRECTORY} amd @code{O_PATH} flags.
And also mention that the file name argument must be non-empty in this
case?
next prev parent reply other threads:[~2020-05-12 7:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 9:30 Florian Weimer
2020-04-30 9:39 ` Andreas Schwab
2020-04-30 10:21 ` Florian Weimer
2020-04-30 10:32 ` Andreas Schwab
2020-04-30 11:01 ` Michael Kerrisk
2020-04-30 11:15 ` Michael Kerrisk
2020-04-30 11:35 ` Michael Kerrisk (man-pages)
2020-05-04 5:37 ` Florian Weimer
2020-05-04 8:38 ` Michael Kerrisk (man-pages)
2020-05-04 9:10 ` Florian Weimer
2020-05-04 10:02 ` Michael Kerrisk (man-pages)
2020-05-04 11:16 ` Florian Weimer
2020-05-06 15:48 ` Florian Weimer
2020-05-12 3:05 ` Carlos O'Donell
2020-05-12 3:10 ` Carlos O'Donell
2020-05-12 3:22 ` Carlos O'Donell
2020-05-12 3:35 ` Carlos O'Donell
2020-05-12 6:02 ` Michael Kerrisk
2020-05-12 7:19 ` Florian Weimer [this message]
2020-05-12 7:33 ` Michael Kerrisk (man-pages)
2020-04-30 9:32 Florian Weimer
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=87mu6dzkm1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=mtk.manpages@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).