File tree Expand file tree Collapse file tree 2 files changed +0
-8
lines changed Expand file tree Collapse file tree 2 files changed +0
-8
lines changed Original file line number Diff line number Diff line change @@ -218,10 +218,6 @@ When you pull you can assume a fast-forward strategy (default) or you can
218
218
specify a C<--rebase>, C<--merge> or C<--force> strategy. The latter is the
219
219
same as a C<clone --force> operation, using the current remote and branch.
220
220
221
- When you pull you can assume a fast-forward strategy (default) or you can
222
- specify a C<--rebase>, C<--merge> or C<--force> strategy. The latter is the
223
- same as a C<clone --force> operation, using the current remote and branch.
224
-
225
221
Like the C<clone> command, C<pull> will squash all the changes (since the last
226
222
pull or clone) into one commit. This keeps your mainline history nice and
227
223
clean. You can easily see the subrepo's history with the C<git log> command:
Original file line number Diff line number Diff line change @@ -177,10 +177,6 @@ the same arguments. Keep reading…
177
177
specify a `--rebase`, `--merge` or `--force` strategy. The latter is the same
178
178
as a `clone --force` operation, using the current remote and branch.
179
179
180
- When you pull you can assume a fast-forward strategy (default) or you can
181
- specify a `--rebase`, `--merge` or `--force` strategy. The latter is the same
182
- as a `clone --force` operation, using the current remote and branch.
183
-
184
180
Like the `clone` command, `pull` will squash all the changes (since the last
185
181
pull or clone) into one commit. This keeps your mainline history nice and
186
182
clean. You can easily see the subrepo's history with the `git log` command:
You can’t perform that action at this time.
0 commit comments