| commit | b50c8469cc9a336b22ef37b23711d4547a48bc2b | |
| author | Johan Herland <johan@herland.net> | |
| Thu, 22 May 2008 22:03:00 +0000 (22 18:03 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 23 May 2008 06:35:23 +0000 (22 23:35 -0700) | ||
| tree | 971d03778da07bd76d750bc1f563ebee016fbfad | treesnapshot (tar.gz zip) |
| parent | fabb01996be9f7c8862ab1a6fdfd83c90be5324a | commitdiff |
Add test for cloning with "--reference" repo being a subset of source repo
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@herland.net>
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
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@herland.net>
Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t5700-clone-reference.sh | diffblobblamehistory |