summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/1.7.11.5.txt
diff options
context:
space:
mode:
authorLibravatar Nguyễn Thái Ngọc Duy <pclouds@gmail.com>2013-01-11 16:05:46 +0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-01-11 09:09:30 -0800
commit4dcb167fc3536db0e78c50f239cd3a19afd383fa (patch)
treebce14f1a6fc52523022a0cd324659ef3e4e7801e /Documentation/RelNotes/1.7.11.5.txt
parentGit 1.8.0.3 (diff)
downloadtgif-4dcb167fc3536db0e78c50f239cd3a19afd383fa.tar.xz
fetch: add --unshallow for turning shallow repo into complete one
The user can do --depth=2147483647 (*) for restoring complete repo now. But it's hard to remember. Any other numbers larger than the longest commit chain in the repository would also do, but some guessing may be involved. Make easy-to-remember --unshallow an alias for --depth=2147483647. Make upload-pack recognize this special number as infinite depth. The effect is essentially the same as before, except that upload-pack is more efficient because it does not have to traverse to the bottom anymore. The chance of a user actually wanting exactly 2147483647 commits depth, not infinite, on a repository with a history that long, is probably too small to consider. The client can learn to add or subtract one commit to avoid the special treatment when that actually happens. (*) This is the largest positive number a 32-bit signed integer can contain. JGit and older C Git store depth as "int" so both are OK with this number. Dulwich does not support shallow clone. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.7.11.5.txt')
0 files changed, 0 insertions, 0 deletions