diff options
| author | Junio C Hamano <gitster@pobox.com> | 2017-09-10 17:02:55 +0900 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2017-09-10 17:02:55 +0900 |
| commit | 78ad09403c0c87ae52573bbac2fa7e093152891d (patch) | |
| tree | 6bb756e0eb4ff1dd98ab5e2b97b5e325bdd6e800 /Documentation | |
| parent | 648a50a08ad3d6718899a30a438ff97b4bdda342 (diff) | |
| parent | 9d89b35526b54c3ba33371b184a1ba6e30f8f46f (diff) | |
| download | git-78ad09403c0c87ae52573bbac2fa7e093152891d.tar.gz | |
Merge branch 'mg/killed-merge' into maint
Killing "git merge --edit" before the editor returns control left
the repository in a state with MERGE_MSG but without MERGE_HEAD,
which incorrectly tells the subsequent "git commit" that there was
a squash merge in progress. This has been fixed.
* mg/killed-merge:
merge: save merge state earlier
merge: split write_merge_state in two
merge: clarify call chain
Documentation/git-merge: explain --continue
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/git-merge.txt | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt index 04fdd8cf08..f90faf7aaa 100644 --- a/Documentation/git-merge.txt +++ b/Documentation/git-merge.txt @@ -280,7 +280,10 @@ After seeing a conflict, you can do two things: * Resolve the conflicts. Git will mark the conflicts in the working tree. Edit the files into shape and - 'git add' them to the index. Use 'git commit' to seal the deal. + 'git add' them to the index. Use 'git commit' or + 'git merge --continue' to seal the deal. The latter command + checks whether there is a (interrupted) merge in progress + before calling 'git commit'. You can work through the conflict with a number of tools: |