summaryrefslogtreecommitdiffstats
path: root/git-merge.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2020-04-29 17:03:20 -0700
committerJunio C Hamano <gitster@pobox.com>2020-04-29 17:03:20 -0700
commit67cc2b7cdda7af3a7079b399a8a154d094efc649 (patch)
tree9c4830195de2ffd5ecdfca15e0e04be9bf959a4e /git-merge.txt
parent0dd50943c112dfc70367bd39eb3c88371db2518f (diff)
downloadgit-htmldocs-67cc2b7cdda7af3a7079b399a8a154d094efc649.tar.gz
Autogenerated HTML docs for v2.26.2-447-gd61d2
Diffstat (limited to 'git-merge.txt')
-rw-r--r--git-merge.txt11
1 files changed, 8 insertions, 3 deletions
diff --git a/git-merge.txt b/git-merge.txt
index 092529c61..ec06b2f8c 100644
--- a/git-merge.txt
+++ b/git-merge.txt
@@ -94,7 +94,8 @@ will be appended to the specified message.
--abort::
Abort the current conflict resolution process, and
- try to reconstruct the pre-merge state.
+ try to reconstruct the pre-merge state. If an autostash entry is
+ present, apply it to the worktree.
+
If there were uncommitted worktree changes present when the merge
started, 'git merge --abort' will in some cases be unable to
@@ -102,11 +103,15 @@ reconstruct these changes. It is therefore recommended to always
commit or stash your changes before running 'git merge'.
+
'git merge --abort' is equivalent to 'git reset --merge' when
-`MERGE_HEAD` is present.
+`MERGE_HEAD` is present unless `MERGE_AUTOSTASH` is also present in
+which case 'git merge --abort' applies the stash entry to the worktree
+whereas 'git reset --merge' will save the stashed changes in the stash
+reflog.
--quit::
Forget about the current merge in progress. Leave the index
- and the working tree as-is.
+ and the working tree as-is. If `MERGE_AUTOSTASH` is present, the
+ stash entry will be saved to the stash reflog.
--continue::
After a 'git merge' stops due to conflicts you can conclude the