@@ -61,10 +61,8 @@ this option multiple times, one for each matching ref name.
61
61
See also the `fetch.negotiationAlgorithm` configuration variable
62
62
documented in linkgit:git-config[1].
63
63
64
- ifndef::git-pull[]
65
64
--dry-run::
66
65
Show what would be done, without making any changes.
67
- endif::git-pull[]
68
66
69
67
-f::
70
68
--force::
@@ -95,6 +93,7 @@ ifndef::git-pull[]
95
93
--[no-]write-commit-graph::
96
94
Write a commit-graph after fetching. This overrides the config
97
95
setting `fetch.writeCommitGraph`.
96
+ endif::git-pull[]
98
97
99
98
-p::
100
99
--prune::
@@ -107,6 +106,7 @@ ifndef::git-pull[]
107
106
was cloned with the --mirror option), then they are also
108
107
subject to pruning. Supplying `--prune-tags` is a shorthand for
109
108
providing the tag refspec.
109
+ ifndef::git-pull[]
110
110
+
111
111
See the PRUNING section below for more details.
112
112
@@ -133,7 +133,6 @@ endif::git-pull[]
133
133
behavior for a remote may be specified with the remote.<name>.tagOpt
134
134
setting. See linkgit:git-config[1].
135
135
136
- ifndef::git-pull[]
137
136
--refmap=<refspec>::
138
137
When fetching refs listed on the command line, use the
139
138
specified refspec (can be given more than once) to map the
@@ -154,6 +153,7 @@ ifndef::git-pull[]
154
153
is used (though tags may be pruned anyway if they are also the
155
154
destination of an explicit refspec; see `--prune`).
156
155
156
+ ifndef::git-pull[]
157
157
--recurse-submodules[=yes|on-demand|no]::
158
158
This option controls if and under what conditions new commits of
159
159
populated submodules should be fetched too. It can be used as a
@@ -164,6 +164,7 @@ ifndef::git-pull[]
164
164
when the superproject retrieves a commit that updates the submodule's
165
165
reference to a commit that isn't already in the local submodule
166
166
clone.
167
+ endif::git-pull[]
167
168
168
169
-j::
169
170
--jobs=<n>::
@@ -177,9 +178,11 @@ parallel. To control them independently, use the config settings
177
178
Typically, parallel recursive and multi-remote fetches will be faster. By
178
179
default fetches are performed sequentially, not in parallel.
179
180
181
+ ifndef::git-pull[]
180
182
--no-recurse-submodules::
181
183
Disable recursive fetching of submodules (this has the same effect as
182
184
using the `--recurse-submodules=no` option).
185
+ endif::git-pull[]
183
186
184
187
--set-upstream::
185
188
If the remote is fetched successfully, pull and add upstream
@@ -188,6 +191,7 @@ default fetches are performed sequentially, not in parallel.
188
191
see `branch.<name>.merge` and `branch.<name>.remote` in
189
192
linkgit:git-config[1].
190
193
194
+ ifndef::git-pull[]
191
195
--submodule-prefix=<path>::
192
196
Prepend <path> to paths printed in informative messages
193
197
such as "Fetching submodule foo". This option is used
0 commit comments