doc: git-clone: format verbatim words
We also apply the formatting to urls.txt which is included. Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jean-Noël Avila committed
Mar 10, 2024 at 19:10 UTC
d3717e1e9ceccc30910622795ed241163660dab7
2 files changed
+6
-6
Documentation/git-clone.txt
+2
-2
@@ -156,7 +156,7 @@ objects from the source repository into a pack in the cloned repository.
156
157
--[no-]reject-shallow::
158
Fail if the source repository is a shallow repository.
159
- The 'clone.rejectShallow' configuration variable can be used to
159
+ The `clone.rejectShallow` configuration variable can be used to
160
specify the default.
161
162
--bare::
@@ -263,7 +263,7 @@ corresponding `--mirror` and `--no-tags` options instead.
263
branch remote's `HEAD` points at.
264
Further fetches into the resulting repository will only update the
265
remote-tracking branch for the branch this option was used for the
266
- initial cloning. If the HEAD at the remote did not point at any
266
+ initial cloning. If the `HEAD` at the remote did not point at any
267
branch when `--single-branch` clone was made, no remote-tracking
268
branch is created.
269
Documentation/urls.txt
+4
-4
@@ -44,20 +44,20 @@ syntaxes may be used:
44
45
ifndef::git-clone[]
46
These two syntaxes are mostly equivalent, except when cloning, when
47
-the former implies --local option. See linkgit:git-clone[1] for
47
+the former implies `--local` option. See linkgit:git-clone[1] for
48
details.
49
endif::git-clone[]
50
51
ifdef::git-clone[]
52
These two syntaxes are mostly equivalent, except the former implies
53
---local option.
53
+`--local` option.
54
endif::git-clone[]
55
56
-'git clone', 'git fetch' and 'git pull', but not 'git push', will also
56
+`git clone`, `git fetch` and `git pull`, but not `git push`, will also
57
accept a suitable bundle file. See linkgit:git-bundle[1].
58
59
When Git doesn't know how to handle a certain transport protocol, it
60
-attempts to use the 'remote-<transport>' remote helper, if one
60
+attempts to use the `remote-<transport>` remote helper, if one
61
exists. To explicitly request a remote helper, the following syntax
62
may be used:
63