diff options
| author | Sebastian Schuberth <sschuberth@gmail.com> | 2016-01-08 10:18:21 +0100 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-01-08 12:39:58 -0800 |
| commit | fc142811d14d3acb64d1c2057a774fa1573e60cb (patch) | |
| tree | a6e6221b676d47eebd86ca4579986019630b87b4 | |
| parent | 28a1b56932c222b326e4ac0cd480d4e0be72fb1c (diff) | |
| download | git-fc142811d14d3acb64d1c2057a774fa1573e60cb.tar.gz | |
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>
| -rw-r--r-- | Documentation/git-clone.txt | 2 |
1 files changed, 1 insertions, 1 deletions
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 <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. |