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>maint
parent
e7b3a7683c
commit
d3717e1e9c
|
|
@ -156,7 +156,7 @@ objects from the source repository into a pack in the cloned repository.
|
|||
|
||||
--[no-]reject-shallow::
|
||||
Fail if the source repository is a shallow repository.
|
||||
The 'clone.rejectShallow' configuration variable can be used to
|
||||
The `clone.rejectShallow` configuration variable can be used to
|
||||
specify the default.
|
||||
|
||||
--bare::
|
||||
|
|
@ -263,7 +263,7 @@ corresponding `--mirror` and `--no-tags` options instead.
|
|||
branch remote's `HEAD` points at.
|
||||
Further fetches into the resulting repository will only update the
|
||||
remote-tracking branch for the branch this option was used for the
|
||||
initial cloning. If the HEAD at the remote did not point at any
|
||||
initial cloning. If the `HEAD` at the remote did not point at any
|
||||
branch when `--single-branch` clone was made, no remote-tracking
|
||||
branch is created.
|
||||
|
||||
|
|
|
|||
|
|
@ -44,20 +44,20 @@ syntaxes may be used:
|
|||
|
||||
ifndef::git-clone[]
|
||||
These two syntaxes are mostly equivalent, except when cloning, when
|
||||
the former implies --local option. See linkgit:git-clone[1] for
|
||||
the former implies `--local` option. See linkgit:git-clone[1] for
|
||||
details.
|
||||
endif::git-clone[]
|
||||
|
||||
ifdef::git-clone[]
|
||||
These two syntaxes are mostly equivalent, except the former implies
|
||||
--local option.
|
||||
`--local` option.
|
||||
endif::git-clone[]
|
||||
|
||||
'git clone', 'git fetch' and 'git pull', but not 'git push', will also
|
||||
`git clone`, `git fetch` and `git pull`, but not `git push`, will also
|
||||
accept a suitable bundle file. See linkgit:git-bundle[1].
|
||||
|
||||
When Git doesn't know how to handle a certain transport protocol, it
|
||||
attempts to use the 'remote-<transport>' remote helper, if one
|
||||
attempts to use the `remote-<transport>` remote helper, if one
|
||||
exists. To explicitly request a remote helper, the following syntax
|
||||
may be used:
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue