2007-06-07 01:39:05 +02:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
test_description='test local clone'
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
2012-05-26 05:42:53 +02:00
|
|
|
repo_is_hardlinked() {
|
|
|
|
|
find "$1/objects" -type f -links 1 >output &&
|
|
|
|
|
test_line_count = 0 output
|
|
|
|
|
}
|
2007-06-07 01:39:05 +02:00
|
|
|
|
|
|
|
|
test_expect_success 'preparing origin repository' '
|
|
|
|
|
: >file && git add . && git commit -m1 &&
|
|
|
|
|
git clone --bare . a.git &&
|
2007-08-16 05:55:44 +02:00
|
|
|
git clone --bare . x &&
|
|
|
|
|
test "$(GIT_CONFIG=a.git/config git config --bool core.bare)" = true &&
|
2010-10-31 08:30:58 +01:00
|
|
|
test "$(GIT_CONFIG=x/config git config --bool core.bare)" = true &&
|
2009-01-18 07:27:08 +01:00
|
|
|
git bundle create b1.bundle --all &&
|
2009-01-16 13:52:53 +01:00
|
|
|
git bundle create b2.bundle master &&
|
2008-02-29 20:16:19 +01:00
|
|
|
mkdir dir &&
|
2010-10-31 08:30:58 +01:00
|
|
|
cp b1.bundle dir/b3 &&
|
2008-02-29 20:16:19 +01:00
|
|
|
cp b1.bundle b4
|
2007-06-07 01:39:05 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'local clone without .git suffix' '
|
|
|
|
|
git clone -l -s a b &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd b &&
|
2007-08-16 05:55:44 +02:00
|
|
|
test "$(GIT_CONFIG=.git/config git config --bool core.bare)" = false &&
|
2012-05-26 05:42:53 +02:00
|
|
|
git fetch)
|
2007-06-07 01:39:05 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'local clone with .git suffix' '
|
|
|
|
|
git clone -l -s a.git c &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd c && git fetch)
|
2007-06-07 01:39:05 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'local clone from x' '
|
|
|
|
|
git clone -l -s x y &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd y && git fetch)
|
2007-06-07 01:39:05 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'local clone from x.git that does not exist' '
|
2012-05-26 05:42:53 +02:00
|
|
|
test_must_fail git clone -l -s x.git z
|
2007-06-07 01:39:05 +02:00
|
|
|
'
|
|
|
|
|
|
git-clone: aggressively optimize local clone behaviour.
This changes the behaviour of cloning from a repository on the
local machine, by defaulting to "-l" (use hardlinks to share
files under .git/objects) and making "-l" a no-op. A new
option, --no-hardlinks, is also added to cause file-level copy
of files under .git/objects while still avoiding the normal
"pack to pipe, then receive and index pack" network transfer
overhead. The old behaviour of local cloning without -l nor -s
is availble by specifying the source repository with the newly
introduced file:///path/to/repo.git/ syntax (i.e. "same as
network" cloning).
* With --no-hardlinks (i.e. have all .git/objects/ copied via
cpio) would not catch the source repository corruption, and
also risks corrupted recipient repository if an
alpha-particle hits memory cell while indexing and resolving
deltas. As long as the recipient is created uncorrupted, you
have a good back-up.
* same-as-network is expensive, but it would catch the breakage
of the source repository. It still risks corrupted recipient
repository due to hardware failure. As long as the recipient
is created uncorrupted, you have a good back-up.
* The new default on the same filesystem, as long as the source
repository is healthy, it is very likely that the recipient
would be, too. Also it is very cheap. You do not get any
back-up benefit, though.
None of the method is resilient against the source repository
corruption, so let's discount that from the comparison. Then
the difference with and without --no-hardlinks matters primarily
if you value the back-up benefit or not. If you want to use the
cloned repository as a back-up, then it is cheaper to do a clone
with --no-hardlinks and two git-fsck (source before clone,
recipient after clone) than same-as-network clone, especially as
you are likely to do a git-fsck on the recipient if you are so
paranoid anyway.
Which leads me to believe that being able to use file:/// is
probably a good idea, if only for testability, but probably of
little practical value. We default to hardlinked clone for
everyday use, and paranoids can use --no-hardlinks as a way to
make a back-up.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-08-02 08:42:36 +02:00
|
|
|
test_expect_success 'With -no-hardlinks, local will make a copy' '
|
|
|
|
|
git clone --bare --no-hardlinks x w &&
|
2012-05-26 05:42:53 +02:00
|
|
|
! repo_is_hardlinked w
|
git-clone: aggressively optimize local clone behaviour.
This changes the behaviour of cloning from a repository on the
local machine, by defaulting to "-l" (use hardlinks to share
files under .git/objects) and making "-l" a no-op. A new
option, --no-hardlinks, is also added to cause file-level copy
of files under .git/objects while still avoiding the normal
"pack to pipe, then receive and index pack" network transfer
overhead. The old behaviour of local cloning without -l nor -s
is availble by specifying the source repository with the newly
introduced file:///path/to/repo.git/ syntax (i.e. "same as
network" cloning).
* With --no-hardlinks (i.e. have all .git/objects/ copied via
cpio) would not catch the source repository corruption, and
also risks corrupted recipient repository if an
alpha-particle hits memory cell while indexing and resolving
deltas. As long as the recipient is created uncorrupted, you
have a good back-up.
* same-as-network is expensive, but it would catch the breakage
of the source repository. It still risks corrupted recipient
repository due to hardware failure. As long as the recipient
is created uncorrupted, you have a good back-up.
* The new default on the same filesystem, as long as the source
repository is healthy, it is very likely that the recipient
would be, too. Also it is very cheap. You do not get any
back-up benefit, though.
None of the method is resilient against the source repository
corruption, so let's discount that from the comparison. Then
the difference with and without --no-hardlinks matters primarily
if you value the back-up benefit or not. If you want to use the
cloned repository as a back-up, then it is cheaper to do a clone
with --no-hardlinks and two git-fsck (source before clone,
recipient after clone) than same-as-network clone, especially as
you are likely to do a git-fsck on the recipient if you are so
paranoid anyway.
Which leads me to believe that being able to use file:/// is
probably a good idea, if only for testability, but probably of
little practical value. We default to hardlinked clone for
everyday use, and paranoids can use --no-hardlinks as a way to
make a back-up.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-08-02 08:42:36 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'Even without -l, local will make a hardlink' '
|
|
|
|
|
rm -fr w &&
|
|
|
|
|
git clone -l --bare x w &&
|
2012-05-26 05:42:53 +02:00
|
|
|
repo_is_hardlinked w
|
git-clone: aggressively optimize local clone behaviour.
This changes the behaviour of cloning from a repository on the
local machine, by defaulting to "-l" (use hardlinks to share
files under .git/objects) and making "-l" a no-op. A new
option, --no-hardlinks, is also added to cause file-level copy
of files under .git/objects while still avoiding the normal
"pack to pipe, then receive and index pack" network transfer
overhead. The old behaviour of local cloning without -l nor -s
is availble by specifying the source repository with the newly
introduced file:///path/to/repo.git/ syntax (i.e. "same as
network" cloning).
* With --no-hardlinks (i.e. have all .git/objects/ copied via
cpio) would not catch the source repository corruption, and
also risks corrupted recipient repository if an
alpha-particle hits memory cell while indexing and resolving
deltas. As long as the recipient is created uncorrupted, you
have a good back-up.
* same-as-network is expensive, but it would catch the breakage
of the source repository. It still risks corrupted recipient
repository due to hardware failure. As long as the recipient
is created uncorrupted, you have a good back-up.
* The new default on the same filesystem, as long as the source
repository is healthy, it is very likely that the recipient
would be, too. Also it is very cheap. You do not get any
back-up benefit, though.
None of the method is resilient against the source repository
corruption, so let's discount that from the comparison. Then
the difference with and without --no-hardlinks matters primarily
if you value the back-up benefit or not. If you want to use the
cloned repository as a back-up, then it is cheaper to do a clone
with --no-hardlinks and two git-fsck (source before clone,
recipient after clone) than same-as-network clone, especially as
you are likely to do a git-fsck on the recipient if you are so
paranoid anyway.
Which leads me to believe that being able to use file:/// is
probably a good idea, if only for testability, but probably of
little practical value. We default to hardlinked clone for
everyday use, and paranoids can use --no-hardlinks as a way to
make a back-up.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-08-02 08:42:36 +02:00
|
|
|
'
|
|
|
|
|
|
2008-02-20 16:10:17 +01:00
|
|
|
test_expect_success 'local clone of repo with nonexistent ref in HEAD' '
|
|
|
|
|
echo "ref: refs/heads/nonexistent" > a.git/HEAD &&
|
|
|
|
|
git clone a d &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd d &&
|
2008-02-20 16:10:17 +01:00
|
|
|
git fetch &&
|
2012-05-26 05:42:53 +02:00
|
|
|
test ! -e .git/refs/remotes/origin/HEAD)
|
|
|
|
|
'
|
2008-02-20 16:10:17 +01:00
|
|
|
|
2008-02-29 20:16:19 +01:00
|
|
|
test_expect_success 'bundle clone without .bundle suffix' '
|
|
|
|
|
git clone dir/b3 &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd b3 && git fetch)
|
2008-02-29 20:16:19 +01:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'bundle clone with .bundle suffix' '
|
|
|
|
|
git clone b1.bundle &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd b1 && git fetch)
|
2008-02-29 20:16:19 +01:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'bundle clone from b4' '
|
|
|
|
|
git clone b4 bdl &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd bdl && git fetch)
|
2008-02-29 20:16:19 +01:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'bundle clone from b4.bundle that does not exist' '
|
2012-05-26 05:42:53 +02:00
|
|
|
test_must_fail git clone b4.bundle bb
|
2008-02-29 20:16:19 +01:00
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'bundle clone with nonexistent HEAD' '
|
|
|
|
|
git clone b2.bundle b2 &&
|
2012-05-26 05:42:53 +02:00
|
|
|
(cd b2 &&
|
2010-10-31 08:30:58 +01:00
|
|
|
git fetch &&
|
2012-05-26 05:42:53 +02:00
|
|
|
test_must_fail git rev-parse --verify refs/heads/master)
|
2008-02-29 20:16:19 +01:00
|
|
|
'
|
|
|
|
|
|
2009-01-23 01:07:32 +01:00
|
|
|
test_expect_success 'clone empty repository' '
|
|
|
|
|
mkdir empty &&
|
2009-02-11 11:28:03 +01:00
|
|
|
(cd empty &&
|
|
|
|
|
git init &&
|
|
|
|
|
git config receive.denyCurrentBranch warn) &&
|
2009-01-23 01:07:32 +01:00
|
|
|
git clone empty empty-clone &&
|
|
|
|
|
test_tick &&
|
|
|
|
|
(cd empty-clone
|
|
|
|
|
echo "content" >> foo &&
|
|
|
|
|
git add foo &&
|
|
|
|
|
git commit -m "Initial commit" &&
|
|
|
|
|
git push origin master &&
|
|
|
|
|
expected=$(git rev-parse master) &&
|
|
|
|
|
actual=$(git --git-dir=../empty/.git rev-parse master) &&
|
|
|
|
|
test $actual = $expected)
|
|
|
|
|
'
|
|
|
|
|
|
2009-04-20 13:09:37 +02:00
|
|
|
test_expect_success 'clone empty repository, and then push should not segfault.' '
|
|
|
|
|
rm -fr empty/ empty-clone/ &&
|
|
|
|
|
mkdir empty &&
|
|
|
|
|
(cd empty && git init) &&
|
|
|
|
|
git clone empty empty-clone &&
|
2009-04-28 00:12:31 +02:00
|
|
|
(cd empty-clone &&
|
|
|
|
|
test_must_fail git push)
|
2009-04-20 13:09:37 +02:00
|
|
|
'
|
|
|
|
|
|
2011-02-18 05:01:52 +01:00
|
|
|
test_expect_success 'cloning non-existent directory fails' '
|
|
|
|
|
rm -rf does-not-exist &&
|
|
|
|
|
test_must_fail git clone does-not-exist
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'cloning non-git directory fails' '
|
|
|
|
|
rm -rf not-a-git-repo not-a-git-repo-clone &&
|
|
|
|
|
mkdir not-a-git-repo &&
|
|
|
|
|
test_must_fail git clone not-a-git-repo not-a-git-repo-clone
|
|
|
|
|
'
|
|
|
|
|
|
2012-05-30 13:10:16 +02:00
|
|
|
test_expect_success 'cloning file:// does not hardlink' '
|
|
|
|
|
git clone --bare file://"$(pwd)"/a non-local &&
|
|
|
|
|
! repo_is_hardlinked non-local
|
|
|
|
|
'
|
|
|
|
|
|
|
|
|
|
test_expect_success 'cloning a local path with --no-local does not hardlink' '
|
|
|
|
|
git clone --bare --no-local a force-nonlocal &&
|
|
|
|
|
! repo_is_hardlinked force-nonlocal
|
|
|
|
|
'
|
|
|
|
|
|
clone: always set transport options
A clone will always create a transport struct, whether we
are cloning locally or using an actual protocol. In the
local case, we only use the transport to get the list of
refs, and then transfer the objects out-of-band.
However, there are many options that we do not bother
setting up in the local case. For the most part, these are
noops, because they only affect the object-fetching stage
(e.g., the --depth option). However, some options do have a
visible impact. For example, giving the path to upload-pack
via "-u" does not currently work for a local clone, even
though we need upload-pack to get the ref list.
We can just drop the conditional entirely and set these
options for both local and non-local clones. Rather than
keep track of which options impact the object versus the ref
fetching stage, we can simply let the noops be noops (and
the cost of setting the options in the first place is not
high).
The one exception is that we also check that the transport
provides both a "get_refs_list" and a "fetch" method. We
will now be checking the former for both cases (which is
good, since a transport that cannot fetch refs would not
work for a local clone), and we tweak the conditional to
check for a "fetch" only when we are non-local.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2013-09-18 22:35:13 +02:00
|
|
|
test_expect_success 'cloning locally respects "-u" for fetching refs' '
|
|
|
|
|
test_must_fail git clone --bare -u false a should_not_work.git
|
|
|
|
|
'
|
|
|
|
|
|
2007-06-07 01:39:05 +02:00
|
|
|
test_done
|