diff options
author | Junio C Hamano <gitster@pobox.com> | 2018-04-11 11:07:11 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2018-04-11 11:07:11 +0200 |
commit | 8b026edac3104ecc40a68fd58b764fb3c717babb (patch) | |
tree | d42982dc7593d566b4ba43b06f23f86014124d40 /t/t7607-merge-overwrite.sh | |
parent | The third batch for 2.18 (diff) | |
download | git-8b026edac3104ecc40a68fd58b764fb3c717babb.tar.xz git-8b026edac3104ecc40a68fd58b764fb3c717babb.zip |
Revert "Merge branch 'en/rename-directory-detection'"
This reverts commit e4bb62fa1eeee689744b413e29a50b4d1dae6886, reversing
changes made to 468165c1d8a442994a825f3684528361727cd8c0.
The topic appears to inflict severe regression in renaming merges,
even though the promise of it was that it would improve them.
We do not yet know which exact change in the topic was wrong, but in
the meantime, let's play it safe and revert it out of 'master'
before real Git-using projects are harmed.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7607-merge-overwrite.sh')
-rwxr-xr-x | t/t7607-merge-overwrite.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t7607-merge-overwrite.sh b/t/t7607-merge-overwrite.sh index dd8ab7ede1..9c422bcd7c 100755 --- a/t/t7607-merge-overwrite.sh +++ b/t/t7607-merge-overwrite.sh @@ -92,7 +92,7 @@ test_expect_success 'will not overwrite removed file with staged changes' ' test_cmp important c1.c ' -test_expect_success 'will not overwrite unstaged changes in renamed file' ' +test_expect_failure 'will not overwrite unstaged changes in renamed file' ' git reset --hard c1 && git mv c1.c other.c && git commit -m rename && |