Skip to content

Commit

Permalink
Documentation: suggest reset --merge in How Merge Works section
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Jonathan Nieder authored and Thomas Rast committed Jan 24, 2010
1 parent 35e9d63 commit ed4a6ba
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Documentation/git-merge.txt
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,6 @@ include::merge-options.txt[]
include::merge-strategies.txt[]


If you tried a merge which resulted in complex conflicts and
want to start over, you can recover with 'git reset'.

HOW MERGE WORKS
---------------

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

If you tried a merge which resulted in complex conflicts and
want to start over, you can recover with `git reset --merge`.

HOW CONFLICTS ARE PRESENTED
---------------------------

Expand Down

0 comments on commit ed4a6ba

Please sign in to comment.