fetch: elaborate --depth action
--depth is explained as deepen, but the way it's applied, it can shorten the history as well. Keen users may have noticed the implication by the phrase "the specified number of commits from the tip of each remote branch". Put "shorten" in the description to make it clearer. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Nguyễn Thái Ngọc Duy committed
Jan 11, 2013 at 16:05 UTC
cfb70e1fa506e79f337e716ed4813c6caa428644
1 file changed
+1
-1
Documentation/fetch-options.txt
+1
-1
@@ -8,7 +8,7 @@
8
option old data in `.git/FETCH_HEAD` will be overwritten.
9
10
--depth=<depth>::
11
- Deepen the history of a 'shallow' repository created by
11
+ Deepen or shorten the history of a 'shallow' repository created by
12
`git clone` with `--depth=<depth>` option (see linkgit:git-clone[1])
13
to the specified number of commits from the tip of each remote
14
branch history. Tags for the deepened commits are not fetched.