[PATCH v2 3/3] fetch: elaborate --depth action
- From
Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
- Date
- Jan 11, 2013, 09:05 UTC
- Message-ID
- <1357895148-30909-3-git-send-email-pclouds@gmail.com>
- In-Reply-To
- <1357895148-30909-1-git-send-email-pclouds@gmail.com>
--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> --- Documentation/fetch-options.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/fetch-options.txt b/Documentation/fetch-options.txt index 8a0449c..fb92b02 100644 --- a/Documentation/fetch-options.txt +++ b/Documentation/fetch-options.txt @@ -8,7 +8,7 @@ option old data in `.git/FETCH_HEAD` will be overwritten. --depth=<depth>:: - Deepen the history of a 'shallow' repository created by + Deepen or shorten the history of a 'shallow' repository created by `git clone` with `--depth=<depth>` option (see linkgit:git-clone[1]) to the specified number of commits from the tip of each remote branch history. Tags for the deepened commits are not fetched.
-- 1.8.0.rc2.23.g1fb49df