development/git
development/git
1
0
Fork 0
mirror of https://github.com/git/git synced 2024-08-25 02:35:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

git-clone --reference: saner handling of borrowed symrefs.

Browse source 
When using --reference to borrow objects from a neighbouring
repository while cloning, we copy the entire set of refs under
temporary "refs/reference-tmp/refs" space and set up the object
alternates.  However, a textual symref copied this way would not
point at the right place, and causes later steps to emit error
messages (which is harmless but still alarming).  This is most
visible when using a clone created with the separate-remote
layout as a reference, because such a repository would have
refs/remotes/origin/HEAD with 'ref: refs/remotes/origin/master'
as its contents.

Although we do not create symbolic-link based refs anymore, they
have the same problem because they are always supposed to be
relative to refs/ hierarchy (we dereference by hand, so it only
is good for HEAD and nothing else).

In either case, the solution is simply to remove them after
copying under refs/reference-tmp; if a symref points at a true
ref, that true ref itself is enough to ensure that objects
reachable from it do not needlessly get fetched.

Signed-off-by: Junio C Hamano <junkio@cox.net>
This commit is contained in:
Junio C Hamano 2007-02-04 03:25:12 -08:00
parent ec80489132
commit 1f7d1a53fe
2 changed files with 67 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

29
git-clone.sh
View file

@ -190,7 +190,34 @@ then
(cd "$GIT_DIR/refs" &&
mkdir reference-tmp &&
cd reference-tmp &&
tar xf -)
tar xf - &&
find refs ! -type d -print |
while read ref
do
if test -h "$ref"
then
# Old-style symbolic link ref. Not likely
# to appear under refs/ but we might as well
# deal with them.
:
elif test -f "$ref"
then
point=$(cat "$ref") &&
case "$point" in
'ref: '*) ;;
*) continue ;;
esac
fi
# The above makes true ref to 'continue' and
# we will come here when we are looking at
# symbolic link ref or a textual symref (or
# garbage, like fifo).
# The true ref pointed at by it is enough to
# ensure that we do not fetch objects reachable
# from it.
rm -f "$ref"
done
)
else
die "reference repository '$reference' is not a local directory."
fi

40
t/t5700-clone-reference.sh
View file

@ -26,7 +26,7 @@ git prune'
cd "$base_dir"
test_expect_success 'cloning with reference' \
test_expect_success 'cloning with reference (-l -s)' \
'git clone -l -s --reference B A C'
cd "$base_dir"
@ -50,6 +50,28 @@ diff expected current'
cd "$base_dir"
test_expect_success 'cloning with reference (no -l -s)' \
'git clone --reference B A D'
cd "$base_dir"
test_expect_success 'existence of info/alternates' \
'test `wc -l <D/.git/objects/info/alternates` = 1'
cd "$base_dir"
test_expect_success 'pulling from reference' \
'cd D && git pull ../B'
cd "$base_dir"
test_expect_success 'that reference gets used' \
'cd D && echo "0 objects, 0 kilobytes" > expected &&
git count-objects > current &&
diff expected current'
cd "$base_dir"
test_expect_success 'updating origin' \
'cd A &&
echo third > file3 &&
@ -75,4 +97,20 @@ diff expected current'
cd "$base_dir"
test_expect_success 'pulling changes from origin' \
'cd D &&
git pull origin'
cd "$base_dir"
# the 5 local objects are expected; file3 blob, commit in A to add it
# and its tree, and 2 are our tree and the merge commit.
test_expect_success 'check objects expected to exist locally' \
'cd D &&
echo "5 objects" > expected &&
git count-objects | cut -d, -f1 > current &&
diff expected current'
cd "$base_dir"
test_done