From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: David Symonds <dsymonds@gmail.com>
Cc: Junio C Hamano <junio@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-checkout: Handle relative paths containing "..".
Date: Thu, 8 Nov 2007 14:25:17 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711081420570.4362@racer.site> (raw)
In-Reply-To: <ee77f5c20711080510i138729b9vb0b9ad485cb2db3@mail.gmail.com>
Hi,
On Fri, 9 Nov 2007, David Symonds wrote:
> On Nov 8, 2007 7:30 PM, Junio C Hamano <junio@pobox.com> wrote:
> >
> > Have you tested this patch from the toplevel of any tree, where
> > "git-rev-parse --show-cdup" would yield an empty string?
>
> No, I didn't. Arguably, "git-rev-parse --show-cdup" should always return
> a path to the top-level, which would make this kind of construction much
> simpler.
As it is, we have a convenience function for this, to make it much
simpler: cd_to_toplevel in git-sh-setup.
> > I also wonder how this patch (with an obvious fix to address the above
> > point) would interact with GIT_DIR and/or GIT_WORK_TREE in the
> > environment.
>
> No idea. I'm still learning my way around the git codebase, so I was
> hoping for some review and feedback from more experienced Gits.
It _should_ work with GIT_DIR/GIT_WORK_TREE, as the full name is relative
to the project root, and that's exactly where cd_to_toplevel is jumping
to. And the first call to ls-files should make certain that the paths are
correct, so there should be no confusion either.
But yes, I have been burnt by that work tree stuff too many times, so I'd
appreciate tests for that (both positive and negative ones).
Ciao,
Dscho
prev parent reply other threads:[~2007-11-08 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 2:33 [PATCH] git-checkout: Handle relative paths containing ".." David Symonds
2007-11-08 8:30 ` Junio C Hamano
2007-11-08 13:10 ` David Symonds
2007-11-08 14:25 ` Johannes Schindelin [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=Pine.LNX.4.64.0711081420570.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=junio@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).