From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: RFA: Use lrealpath instead of gdb_realpath
Date: Mon, 30 May 2005 18:32:00 -0000 [thread overview]
Message-ID: <uis118h22.fsf@gnu.org> (raw)
In-Reply-To: <20050529190550.GF11936@trixie.casa.cgf.cx> (message from Christopher Faylor on Sun, 29 May 2005 15:05:50 -0400)
> Date: Sun, 29 May 2005 15:05:50 -0400
> From: Christopher Faylor <me@cgf.cx>
>
> but I'm not sure that c would meet the criteria of whatever else is
> using lrealpath.
I don't see how can it not meet those criteria, since realpath and
canonicalize_file_name both behave like this.
prev parent reply other threads:[~2005-05-30 16:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 23:59 Daniel Jacobowitz
2005-05-29 1:59 ` Christopher Faylor
2005-05-29 14:21 ` Eli Zaretskii
2005-05-29 14:23 ` Daniel Jacobowitz
2005-05-29 17:49 ` Christopher Faylor
2005-05-29 18:22 ` Eli Zaretskii
2005-05-29 18:27 ` Christopher Faylor
2005-05-30 16:54 ` Eli Zaretskii
2005-05-29 19:28 ` Daniel Jacobowitz
2005-05-29 20:16 ` Christopher Faylor
2005-05-30 15:14 ` Christopher Faylor
2005-05-30 18:32 ` Eli Zaretskii [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=uis118h22.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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