author | Johannes Schindelin <Johannes.Schindelin@gmx.de> | |
Mon, 30 Oct 2006 19:09:29 +0000 (20:09 +0100) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Fri, 24 Nov 2006 23:42:49 +0000 (15:42 -0800) | ||
commit | 016e6ccbe03438454777e43dd73d67844296a3fd | |
tree | f8fa1544f7abf2d4d16217adceaec6901a9635c9 | tree | snapshot |
parent | ed09aef06fda2ba06a7412e3fa43ab1c3449f723 | commit | diff |
allow cloning a repository "shallowly"
By specifying a depth, you can now clone a repository such that
all fetched ancestor-chains' length is at most "depth". For example,
if the upstream repository has only 2 branches ("A" and "B"), which
are linear, and you specify depth 3, you will get A, A~1, A~2, A~3,
B, B~1, B~2, and B~3. The ends are automatically made shallow
commits.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
By specifying a depth, you can now clone a repository such that
all fetched ancestor-chains' length is at most "depth". For example,
if the upstream repository has only 2 branches ("A" and "B"), which
are linear, and you specify depth 3, you will get A, A~1, A~2, A~3,
B, B~1, B~2, and B~3. The ends are automatically made shallow
commits.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
fetch-pack.c | diff | blob | history | |
git-clone.sh | diff | blob | history | |
upload-pack.c | diff | blob | history |