Skip to content

Commit 01a5774

Browse files
committed
Merge branch 'jc/maint-pull-docfix' into maint
The documentation to "git pull" hinted there is an "-m" option because it incorrectly shared the documentation with "git merge". * jc/maint-pull-docfix: Documentation: "git pull" does not have the "-m" option Documentation: exclude irrelevant options from "git pull"
2 parents a74a682 + 08f19cf commit 01a5774

File tree

2 files changed

+8
-5
lines changed

2 files changed

+8
-5
lines changed

Documentation/git-pull.txt

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -99,10 +99,10 @@ must be given before the options meant for 'git fetch'.
9999
Options related to merging
100100
~~~~~~~~~~~~~~~~~~~~~~~~~~
101101

102-
include::merge-options.txt[]
103-
104102
:git-pull: 1
105103

104+
include::merge-options.txt[]
105+
106106
-r::
107107
--rebase[=false|true|preserve]::
108108
When true, rebase the current branch on top of the upstream

Documentation/merge-options.txt

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,12 @@ inspect and further tweak the merge result before committing.
1414
further edit the auto-generated merge message, so that the user
1515
can explain and justify the merge. The `--no-edit` option can be
1616
used to accept the auto-generated message (this is generally
17-
discouraged). The `--edit` (or `-e`) option is still useful if you are
18-
giving a draft message with the `-m` option from the command line
19-
and want to edit it in the editor.
17+
discouraged).
18+
ifndef::git-pull[]
19+
The `--edit` (or `-e`) option is still useful if you are
20+
giving a draft message with the `-m` option from the command line
21+
and want to edit it in the editor.
22+
endif::git-pull[]
2023
+
2124
Older scripts may depend on the historical behaviour of not allowing the
2225
user to edit the merge log message. They will see an editor opened when

0 commit comments

Comments
 (0)