Skip to content

Commit ed4a6ba

Browse files
jrntrast
authored andcommitted
Documentation: suggest reset --merge in How Merge Works section
The 'merge' manual suggests 'reset' to cancel a merge at the end of the Merge Strategies list. It is more logical to explain this right before explaining how merge conflicts work, so the daunted reader can have a way out when he or she needs it most. While at it, make the advice more dependable and self-contained by providing the --merge option. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Thomas Rast <trast@student.ethz.ch>
1 parent 35e9d63 commit ed4a6ba

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/git-merge.txt

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,6 @@ include::merge-options.txt[]
4545
include::merge-strategies.txt[]
4646

4747

48-
If you tried a merge which resulted in complex conflicts and
49-
want to start over, you can recover with 'git reset'.
50-
5148
HOW MERGE WORKS
5249
---------------
5350

@@ -115,6 +112,9 @@ When there are conflicts, the following happens:
115112
same and the index entries for them stay as they were,
116113
i.e. matching `HEAD`.
117114

115+
If you tried a merge which resulted in complex conflicts and
116+
want to start over, you can recover with `git reset --merge`.
117+
118118
HOW CONFLICTS ARE PRESENTED
119119
---------------------------
120120

0 commit comments

Comments
 (0)