From: Sebastian Schuberth Date: Fri, 08 Jan 2016 09:18:21 GMT Subject: [PATCH] docs: say "commits" in the --depth option wording for git-clone Message-ID: <568F7EDD.9020003@gmail.com> In-Reply-To: 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". --- Documentation/git-clone.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/git-clone.txt b/Documentation/git-clone.txt index 943de8b..789b668 100644 --- a/Documentation/git-clone.txt +++ b/Documentation/git-clone.txt @@ -190,7 +190,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. -- 2.7.0.windows.1