From: Andreas Schwab <schwab@linux-m68k.org>
To: Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Cc: Siddhesh Poyarekar <siddhesh@sourceware.org>,
Iker Pedrosa <ipedrosa@redhat.com>
Subject: Re: [PATCH v1.1] realpath: Bring back GNU extension on ENOENT and EACCES [BZ #28996]
Date: Thu, 31 Mar 2022 16:44:37 +0200 [thread overview]
Message-ID: <87ee2iw59m.fsf@igel.home> (raw)
In-Reply-To: <20220330043502.74482-1-siddhesh@sourceware.org> (Siddhesh Poyarekar via Libc-alpha's message of "Wed, 30 Mar 2022 10:05:02 +0530")
On Mär 30 2022, Siddhesh Poyarekar via Libc-alpha wrote:
> The GNU extension for realpath states that if the path resolution fails
> with ENOENT or EACCES and the resolved buffer is non-NULL, it will
> contain part of the path that failed resolution.
>
> commit 949ad78a189194048df8a253bb31d1d11d919044 broke this when it
> omitted the copy on failure. Bring it back partially to continue
> supporting this GNU extension.
Ok.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
prev parent reply other threads:[~2022-03-31 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 4:35 Siddhesh Poyarekar
2022-03-31 14:44 ` Andreas Schwab [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=87ee2iw59m.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ipedrosa@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@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).