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 <gitster@pobox.com>
Sebastian Schuberth committed
Jan 8, 2016 at 10:18 UTC
fc142811d14d3acb64d1c2057a774fa1573e60cb
1 file changed
+1
-1
Documentation/git-clone.txt
+1
-1
@@ -178,7 +178,7 @@ objects from the source repository into a pack in the cloned repository.
178
179
--depth <depth>::
180
Create a 'shallow' clone with a history truncated to the
181
- specified number of revisions. Implies `--single-branch` unless
181
+ specified number of commits. Implies `--single-branch` unless
182
`--no-single-branch` is given to fetch the histories near the
183
tips of all branches.
184