docs: git-clone: list short form of options first
List the short form of options (e.g.: '-l') before the long form (e.g. '--local'). This is to match the doc of git-add, git-commit, git-clean, git-branch... Signed-off-by: Quentin Nerden <quentin.nerden@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Quentin Nerden committed
Jul 2, 2019 at 07:37 UTC
bfc8c84ed560af8f74be32fa0fd2568e28161678
1 file changed
+9
-9
Documentation/git-clone.txt
+9
-9
@@ -40,8 +40,8 @@ configuration variables.
40
41
OPTIONS
42
-------
43
---local::
43
-l::
44
+--local::
45
When the repository to clone from is on a local machine,
46
this flag bypasses the normal "Git aware" transport
47
mechanism and clones the repository by making a copy of
@@ -62,8 +62,8 @@ Git transport instead.
62
directory instead of using hardlinks. This may be desirable
63
if you are trying to make a back-up of your repository.
64
65
---shared::
65
-s::
66
+--shared::
67
When the repository to clone is on the local machine,
68
instead of using hard links, automatically setup
69
`.git/objects/info/alternates` to share the objects
@@ -115,13 +115,13 @@ objects from the source repository into a pack in the cloned repository.
115
same repository, and this option can be used to stop the
116
borrowing.
117
118
---quiet::
118
-q::
119
+--quiet::
120
Operate quietly. Progress is not reported to the standard
121
error stream.
122
123
---verbose::
123
-v::
124
+--verbose::
125
Run verbosely. Does not affect the reporting of progress status
126
to the standard error stream.
127
@@ -139,8 +139,8 @@ objects from the source repository into a pack in the cloned repository.
139
When multiple `--server-option=<option>` are given, they are all
140
sent to the other side in the order listed on the command line.
141
142
---no-checkout::
142
-n::
143
+--no-checkout::
144
No checkout of HEAD is performed after the clone is complete.
145
146
--bare::
@@ -163,13 +163,13 @@ objects from the source repository into a pack in the cloned repository.
163
that all these refs are overwritten by a `git remote update` in the
164
target repository.
165
166
---origin <name>::
166
-o <name>::
167
+--origin <name>::
168
Instead of using the remote name `origin` to keep track
169
of the upstream repository, use `<name>`.
170
171
---branch <name>::
171
-b <name>::
172
+--branch <name>::
173
Instead of pointing the newly created HEAD to the branch pointed
174
to by the cloned repository's HEAD, point to `<name>` branch
175
instead. In a non-bare repository, this is the branch that will
@@ -177,8 +177,8 @@ objects from the source repository into a pack in the cloned repository.
177
`--branch` can also take tags and detaches the HEAD at that commit
178
in the resulting repository.
179
180
---upload-pack <upload-pack>::
180
-u <upload-pack>::
181
+--upload-pack <upload-pack>::
182
When given, and the repository to clone from is accessed
183
via ssh, this specifies a non-default path for the command
184
run on the other end.
@@ -187,8 +187,8 @@ objects from the source repository into a pack in the cloned repository.
187
Specify the directory from which templates will be used;
188
(See the "TEMPLATE DIRECTORY" section of linkgit:git-init[1].)
189
190
---config <key>=<value>::
190
-c <key>=<value>::
191
+--config <key>=<value>::
192
Set a configuration variable in the newly-created repository;
193
this takes effect immediately after the repository is
194
initialized, but before the remote history is fetched or any