From: Paul Eggert <eggert@cs.ucla.edu>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/3] <fd_to_filename.h>: Add type safety and port to Hurd
Date: Mon, 17 Feb 2020 11:14:21 -0800 [thread overview]
Message-ID: <1f24c458-0282-c2bd-cf8e-d76b43688a2a@cs.ucla.edu> (raw)
In-Reply-To: <cad1883e-d9de-14a2-e28d-2d53c034e2a4@linaro.org>
On 2/17/20 10:59 AM, Adhemerval Zanella wrote:
> So the question is if it still worth to keep it in sync with
> gnulib, or if is better to push for a more tailored and clean
> replacement.
Another option would be to clarify which part is used in glibc, and which part
is needed only for Gnulib. We do that in some other files shared between the two
projects, by using "#if _LIBC" and the like.
next prev parent reply other threads:[~2020-02-17 19:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 18:10 [PATCH 0/3] <fd_to_filename.h> improvements Florian Weimer
2020-02-14 18:11 ` [PATCH 1/3] <fd_to_filename.h>: Add type safety and port to Hurd Florian Weimer
2020-02-14 18:43 ` Samuel Thibault
2020-02-14 19:08 ` Adhemerval Zanella
2020-02-14 20:21 ` Florian Weimer
2020-02-14 20:28 ` Paul Eggert
2020-02-15 13:16 ` Florian Weimer
2020-02-16 0:02 ` Paul Eggert
2020-02-17 15:18 ` Florian Weimer
2020-02-17 18:26 ` Paul Eggert
2020-02-17 18:59 ` Adhemerval Zanella
2020-02-17 19:14 ` Paul Eggert [this message]
2020-02-14 18:11 ` [PATCH 2/3] Linux: Port ttyname, ttyname_r to <fd_file_name.h> Florian Weimer
2020-02-14 18:11 ` [PATCH 3/3] Linux: Port fexecve to <fd_to_filename.h> 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f24c458-0282-c2bd-cf8e-d76b43688a2a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
/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).