From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/5] Add is_absolute_path(), make_absolute_path() and normalize_path()
Date: Thu, 26 Jul 2007 14:58:59 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707261456040.14781@racer.site> (raw)
In-Reply-To: <7v1wevac63.fsf@assigned-by-dhcp.cox.net>
Hi,
On Wed, 25 Jul 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > +/* strip out .. and . */
> > +char *normalize_path(char *path)
> > +{
>
> This always makes one worry what should happen when foo/../bar
> is _not_ bar in reality (i.e. foo is symlink to a directory
> elsewhere).
>
> It depends on what kind of "path" you feed to the function (and
> its caller, make_absolute_path()). If you always feed a path
> >from the index (or a path obtained by recursively reading a
> tree), it is Ok. If it is arbitrary path obtained from the user
> or the filesystem, it is not.
Agree. Maybe a comment above the function, like
/*
* The function normalize_path() converts ".." and "." names in
* the given path so that "foo/../bar/./" will come out as "bar".
*
* Note: normalize_path() does not follow symlinks, so if "foo" is
* a symlink in the example above, the result will not work as
* expected.
*/
Hmm?
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-26 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 6:24 [PATCH 1/5] Add is_absolute_path(), make_absolute_path() and normalize_path() Johannes Schindelin
2007-07-26 6:53 ` Junio C Hamano
2007-07-26 13:58 ` Johannes Schindelin [this message]
2007-07-26 18:46 ` Junio C Hamano
2007-07-26 19:02 ` Johannes Schindelin
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=Pine.LNX.4.64.0707261456040.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).