summaryrefslogtreecommitdiff
path: root/t/t5100/info0006
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2018-11-12 15:25:58 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-11-13 12:04:00 +0900
commit85f8d9da2182690461e05034a4a697f766bb8eb1 (patch)
tree22fa8db06b0a2edab4274d12c6ab73b4395018af /t/t5100/info0006
parentrebase -r: demonstrate bug with conflicting merges (diff)
downloadtgif-85f8d9da2182690461e05034a4a697f766bb8eb1.tar.xz
rebase -r: do not write MERGE_HEAD unless needed
When we detect that a `merge` can be skipped because the merged commit is already an ancestor of HEAD, we do not need to commit, therefore writing the MERGE_HEAD file is useless. It is actually worse than useless: a subsequent `git commit` will pick it up and think that we want to merge that commit, still. To avoid that, move the code that writes the MERGE_HEAD file to a location where we already know that the `merge` cannot be skipped. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5100/info0006')
0 files changed, 0 insertions, 0 deletions