Skip to content

Commit 08f19cf

Browse files
committed
Documentation: "git pull" does not have the "-m" option
Even though "--[no-]edit" can be used with "git pull", the explanation of the interaction between this option and the "-m" option does not make sense within the context of "git pull". Use the conditional inclusion mechanism to remove this part from "git pull" documentation, while keeping it for "git merge". Reported-by: Ivan Zakharyaschev Signed-off-by: Junio C Hamano <[email protected]>
1 parent 8be1d04 commit 08f19cf

File tree

1 file changed

+6
-3
lines changed

1 file changed

+6
-3
lines changed

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)