The first test in this series tests "git clone -l -s --reference B A C", where repo B is a superset of repo A (A has one commit, B has the same commit plus another). In this case, all objects to be cloned are already present in B. However, we should also test the case where the "--reference" repo is a _subset_ of the source repo (e.g. "git clone -l -s --reference A B C"), i.e. some objects are not available in the "--reference" repo, and will have to be found in the source repo. Signed-off-by: Johan Herland <johan@xxxxxxxxxxx> --- On Sunday 02 March 2008, Daniel Barkalow wrote: > In any case, I've got my current version at > > git://iabervon.org/~barkalow/git.git builtin-clone Thanks, it already looks much better than the initial version. :) However, this added test currently fails for me with the following output: repo is /home/johan/git/git/t/trash/B/.git dir is E Initialize E/.git Initialized empty Git repository in E/.git/ Okay Wrote /home/johan/git/git/t/trash/A/.git/objects to E/.git/objects/info/alternates Wrote /home/johan/git/git/t/trash/B/.git/objects to E/.git/objects/info/alternates Get for /home/johan/git/git/t/trash/B/.git error: Trying to write ref refs/remotes/origin/master with nonexistant object 276cf9e94287a7c4e6f79b2724460e9650fa4871 fatal: Cannot update the ref 'refs/remotes/origin/master'. Remove junk E/.git Remove junk E The same test work well with git-clone.sh. Not sure what's going on here, yet, but I thought I'd give you a heads up. ...Johan t/t5700-clone-reference.sh | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/t/t5700-clone-reference.sh b/t/t5700-clone-reference.sh index b6a5486..d318780 100755 --- a/t/t5700-clone-reference.sh +++ b/t/t5700-clone-reference.sh @@ -113,4 +113,9 @@ diff expected current' cd "$base_dir" +test_expect_success 'cloning with reference being subset of source (-l -s)' \ +'git clone -l -s --reference A B E' + +cd "$base_dir" + test_done -- 1.5.4.3.328.gcaed -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
