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