summaryrefslogtreecommitdiff
path: root/t
diff options
context:
space:
mode:
authorYasushi SHOJI <yashi@atmark-techno.com>2006-10-14 12:02:51 (GMT)
committerJunio C Hamano <junkio@cox.net>2006-10-15 01:22:04 (GMT)
commitced78b3907dd60d8289ad5385ffcfd3339149957 (patch)
tree495457faf1f65f0d983ecc20029371f5e5e75f5c /t
parentd988b82232bb8f5826a1619fd4dcba1a5a330f27 (diff)
downloadgit-ced78b3907dd60d8289ad5385ffcfd3339149957.zip
git-ced78b3907dd60d8289ad5385ffcfd3339149957.tar.gz
git-ced78b3907dd60d8289ad5385ffcfd3339149957.tar.bz2
clone: the given repository dir should be relative to $PWD
the repository argument for git-clone should be relative to $PWD instead of the given target directory. The old behavior gave us surprising success and you need a few minute to know why it worked. GIT_DIR is already exported so no need to cd into $D. And this makes $PWD for git-fetch-pack, which is the actual command to take the given repository dir, the same as git-clone. Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 't')
-rwxr-xr-xt/t5600-clone-fail-cleanup.sh6
1 files changed, 6 insertions, 0 deletions
diff --git a/t/t5600-clone-fail-cleanup.sh b/t/t5600-clone-fail-cleanup.sh
index 0c6a363..041be04 100755
--- a/t/t5600-clone-fail-cleanup.sh
+++ b/t/t5600-clone-fail-cleanup.sh
@@ -25,6 +25,12 @@ test_create_repo foo
# clone doesn't like it if there is no HEAD. Is that a bug?
(cd foo && touch file && git add file && git commit -m 'add file' >/dev/null 2>&1)
+# source repository given to git-clone should be relative to the
+# current path not to the target dir
+test_expect_failure \
+ 'clone of non-existent (relative to $PWD) source should fail' \
+ 'git-clone ../foo baz'
+
test_expect_success \
'clone should work now that source exists' \
'git-clone foo bar'