From: Jeff King <peff@peff.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] HOME must be set before calling git-init when creating test repositories
Date: Sat, 26 Mar 2011 10:11:18 -0400 [thread overview]
Message-ID: <20110326141118.GA3475@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTi=+SZGxLyP8vFPpmK8DZvke6-Tu-crwq5+89qWx@mail.gmail.com>
On Sat, Mar 26, 2011 at 11:08:06AM +0100, Alex Riesen wrote:
> >> Oh, it does. That's why the second patch (prefixed "[PATCH, fixed]").
> >> It makes HOME to be "$(pwd)/somewhere-else", or precisely:
> >>
> >> HOME="$(pwd)"/"$test"
> >> export HOME
> >
> > What happens to people who has non-empty "$root", iow, their $test begins
> > with '/'?
>
> It's still under $test then.
No, it's totally broken. $(pwd)/$test is nonsensical. The code right
above your change guarantees that $test is an absolute path, either
because the user gave us an absolute $root or because it has been
prepended with $TEST_DIRECTORY (which itself comes from $(pwd)).
So the change you want is HOME=$test. But note that the code looks like
this then:
HOME=$test
export HOME
test_create_repo "$test"
cd -P "$test"
meaning that test_create_repo sees a non-existent HOME. I don't
think that matters, but if it did, you could do:
HOME=$TEST_DIRECTORY
export HOME
test_create_repo "$test"
cd -P "$test"
HOME=$test
-Peff
next prev parent reply other threads:[~2011-03-26 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 20:05 [PATCH] HOME must be set before calling git-init when creating test repositories Alex Riesen
2011-03-25 20:44 ` [PATCH, fixed] " Alex Riesen
2011-03-25 20:49 ` [PATCH] " Junio C Hamano
2011-03-25 21:01 ` Alex Riesen
2011-03-25 21:30 ` Junio C Hamano
2011-03-25 21:51 ` Alex Riesen
2011-03-25 22:39 ` Junio C Hamano
2011-03-26 10:08 ` Alex Riesen
2011-03-26 14:11 ` Jeff King [this message]
2011-03-26 18:21 ` Alex Riesen
2011-03-26 18:31 ` Jeff King
2011-03-26 18:42 ` Alex Riesen
2011-03-26 18:46 ` Alex Riesen
2011-03-26 18:48 ` Jeff King
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=20110326141118.GA3475@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=raa.lkml@gmail.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).