From: Florian Weimer <fweimer@redhat.com>
To: Aleksa Sarai <cyphar@cyphar.com>
Cc: "Michael Kerrisk \(man-pages\)" <mtk.manpages@gmail.com>,
pgajdos <pgajdos@suse.cz>,
eppers@posteo.de, linux-man <linux-man@vger.kernel.org>,
libc-alpha@sourceware.org
Subject: Re: openat2.h location (openat2.2)
Date: Thu, 02 Jul 2020 11:41:35 +0200 [thread overview]
Message-ID: <878sg2dzjk.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200630223348.rrr23sfuh7p46top@yavin.dot.cyphar.com> (Aleksa Sarai's message of "Wed, 1 Jul 2020 08:33:48 +1000")
* Aleksa Sarai:
> On 2020-06-30, Michael Kerrisk (man-pages) <mtk.manpages@gmail.com> wrote:
>> [CC += Aleksa, linux-man@]
>>
>> Hello Petr,
>>
>> I'm bringing Aleksa, the creator of the system call, into CC.
>>
>> Aleksa, the issue is that the header file (<openat2.h>) documented in
>> the manual page that you sent does not (yet) exist (and the bug
>> reporter therefore suggests that the manual page should say to include
>> <linux/openat2.h>.
>>
>> I'm guessing that there is (or was) a plan to add a <openat2.h> header
>> file to glibc. What is the status?
>
> Yes, Florian asked me to put the openat2 definitions into a separate
> header (openat2.h) so that it could be just copied by glibc rather than
> having to do any more hacks around <fcntl.h>.
We still need to document the original *at functions. 8-( That's a
precondition for adding openat2 (which should come with its own
documentation right from the start).
<https://sourceware.org/pipermail/libc-alpha/2020-May/113545.html>
> I guess those plans haven't come to fruition yet? I'm fine with telling
> users to use <linux/openat2.h> in the meantime.
If we include <linux/openat2.h> from the glibc header, the transition
should be unproblematic because there won't be any multi-definition
errors.
Thanks,
Florian
prev parent reply other threads:[~2020-07-02 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200630141703.GB12757@laura.suse.cz>
2020-06-30 19:35 ` openat2.h location (openat2.2) Michael Kerrisk (man-pages)
2020-06-30 22:33 ` Aleksa Sarai
2020-07-02 9:41 ` Florian Weimer [this message]
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=878sg2dzjk.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=cyphar@cyphar.com \
--cc=eppers@posteo.de \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=pgajdos@suse.cz \
/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 NNTP newsgroup(s).