From: Paul Eggert <eggert@cs.ucla.edu>
To: Bastien ROUCARIES <roucaries.bastien@gmail.com>,
bug-gnulib <bug-gnulib@gnu.org>, Eric Blake <eblake@redhat.com>
Subject: Re: Time to push passfd API to posix ?
Date: Tue, 27 Apr 2021 18:03:57 -0700 [thread overview]
Message-ID: <af1d3b1b-c846-2957-498b-12621059fc5c@cs.ucla.edu> (raw)
In-Reply-To: <CAE2SPAY0uKdDcsmyn9sX_-m7DuGvW1JHiWYcw2M7OPJjEceX1g@mail.gmail.com>
On 4/27/21 3:49 PM, Bastien ROUCARIES wrote > It have been 10 year that
we invented passfd API, and it was a huge success.> > I think it is time
to submit this API to next revision of POSIX> > What do you think?
Although I don't use it, it looks like a good API for standardization.
I suggest adding an int flags arg to sendfd first, in case sendfd needs
to be extended later (say, someone wants to pass some flags to sendmsg?).
prev parent reply other threads:[~2021-04-28 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 22:49 Time to push passfd API to posix ? Bastien ROUCARIES
2021-04-28 1:03 ` Paul Eggert [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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af1d3b1b-c846-2957-498b-12621059fc5c@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bug-gnulib@gnu.org \
--cc=eblake@redhat.com \
--cc=roucaries.bastien@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).