From: Sebastian Schuberth Date: Fri, 8 Jan 2016 09:18:21 +0000 (+0100) Subject: docs: say "commits" in the --depth option wording for git-clone X-Git-Tag: v2.7.1~2^2~1 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=fc142811d14d3acb64d1c2057a774fa1573e60cb;p=git docs: say "commits" in the --depth option wording for git-clone It is not wrong to talk about "revisions" here, but in this context revisions are always commits, and that is how we already name it in the git-fetch docs. So align the docs by always referring to "commits". Signed-off-by: Junio C Hamano --- diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index dd8271478a..4df1af1230 100644 --- a/Documentation/git-clone.txt +++ b/Documentation/git-clone.txt @@ -178,7 +178,7 @@ objects from the source repository into a pack in the cloned repository. --depth :: Create a 'shallow' clone with a history truncated to the - specified number of revisions. Implies `--single-branch` unless + specified number of commits. Implies `--single-branch` unless `--no-single-branch` is given to fetch the histories near the tips of all branches.