aboutsummaryrefslogtreecommitdiff
path: root/Documentation/technical
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2013-02-01 12:39:24 -0800
committerJunio C Hamano <gitster@pobox.com>2013-02-01 12:39:24 -0800
commit2532d891a4aab003a5ce19f04509fd8549754485 (patch)
treedd423e056e45994a8af8ee7c9e174209ece868f2 /Documentation/technical
parent9a6c84e6e9078b0ef4fd2c50b200e8552a28c6fa (diff)
parentcfb70e1fa506e79f337e716ed4813c6caa428644 (diff)
downloadgit-2532d891a4aab003a5ce19f04509fd8549754485.tar.gz
git-2532d891a4aab003a5ce19f04509fd8549754485.tar.xz
Merge branch 'nd/fetch-depth-is-broken'
"git fetch --depth" was broken in at least three ways. The resulting history was deeper than specified by one commit, it was unclear how to wipe the shallowness of the repository with the command, and documentation was misleading. * nd/fetch-depth-is-broken: fetch: elaborate --depth action upload-pack: fix off-by-one depth calculation in shallow clone fetch: add --unshallow for turning shallow repo into complete one
Diffstat (limited to 'Documentation/technical')
-rw-r--r--Documentation/technical/shallow.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/Documentation/technical/shallow.txt b/Documentation/technical/shallow.txt
index 0502a5471..ea2f69faf 100644
--- a/Documentation/technical/shallow.txt
+++ b/Documentation/technical/shallow.txt
@@ -53,3 +53,6 @@ It also writes an appropriate $GIT_DIR/shallow.
You can deepen a shallow repository with "git-fetch --depth 20
repo branch", which will fetch branch from repo, but stop at depth
20, updating $GIT_DIR/shallow.
+
+The special depth 2147483647 (or 0x7fffffff, the largest positive
+number a signed 32-bit integer can contain) means infinite depth.