summaryrefslogtreecommitdiff
path: root/t/t5515/fetch.br-config-explicit_config-explicit
diff options
context:
space:
mode:
authorLibravatar Phil Hord <hordp@cisco.com>2013-01-12 15:46:01 -0500
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-01-14 09:15:39 -0800
commit986977847e6fb46448fc9c567292ccd2a93d40b3 (patch)
tree0f98417d53fae9b118692e9ad8a1bc62976d5e2c /t/t5515/fetch.br-config-explicit_config-explicit
parentMerge branch 'nh/empty-rebase' (diff)
downloadtgif-986977847e6fb46448fc9c567292ccd2a93d40b3.tar.xz
rebase --preserve-merges: keep all merge commits including empty ones
Since 90e1818f9a (git-rebase: add keep_empty flag, 2012-04-20) 'git rebase --preserve-merges' fails to preserve empty merge commits unless --keep-empty is also specified. Merge commits should be preserved in order to preserve the structure of the rebased graph, even if the merge commit does not introduce changes to the parent. Teach rebase not to drop merge commits only because they are empty. A special case which is not handled by this change is for a merge commit whose parents are now the same commit because all the previous different parents have been dropped as a result of this rebase or some previous operation. Signed-off-by: Phil Hord <hordp@cisco.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t5515/fetch.br-config-explicit_config-explicit')
0 files changed, 0 insertions, 0 deletions