summaryrefslogtreecommitdiffstats
path: root/t/t4013/diff.format-patch_--inline_--stdout_initial..master
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2007-01-26 04:07:34 -0500
committerShawn O. Pearce <spearce@spearce.org>2007-01-26 04:07:34 -0500
commitdff7e88febf85b1b8b1b789cd7c99434b70fb19b (patch)
treeb2c77682237b3c204b43d502746f19a2c39304d7 /t/t4013/diff.format-patch_--inline_--stdout_initial..master
parentee3cfb595415e2f076d5b90efba83088e5af961c (diff)
downloadgit-dff7e88febf85b1b8b1b789cd7c99434b70fb19b.tar.gz
git-dff7e88febf85b1b8b1b789cd7c99434b70fb19b.zip
git-gui: Don't allow users to commit a bad octopus merge.
If an octopus merge goes horribly wrong git-merge will leave the working directory and index dirty, but will not leave behind a MERGE_HEAD file for a later commit. Consequently we won't know its a merge commit and instead would let the user resolve the conflicts and commit a single-parent commit, which is wrong. So now if an octopus merge fails we notify the user that the merge did not work, tell them we will reset the working directory, and suggest that they merge one branch at a time. This prevents the user from committing a bad octopus merge. Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Diffstat (limited to 't/t4013/diff.format-patch_--inline_--stdout_initial..master')
0 files changed, 0 insertions, 0 deletions