aboutsummaryrefslogtreecommitdiff
path: root/builtin-merge-recursive.c
diff options
context:
space:
mode:
authorMarius Storm-Olsen <marius@trolltech.com>2008-06-09 22:22:37 +0100
committerJunio C Hamano <gitster@pobox.com>2008-06-09 15:37:44 -0700
commiteea982843e34da679689f7c53a4874894a225e9f (patch)
treee190da02b7840c896719432045ecfb83745bee9d /builtin-merge-recursive.c
parent170e095a9cfe31617162e8a9b5063b8bc38af82b (diff)
downloadgit-eea982843e34da679689f7c53a4874894a225e9f.tar.gz
git-eea982843e34da679689f7c53a4874894a225e9f.tar.xz
Add testcase for merging in a CRLF repo
If you work on a repo with core.autocrlf == true, you would expect every text file to have CRLF EOLs. However, if you by some operation, get a conflict, then the conflicted file has LF EOLs. Now, of course you'd go about resolving the files conflict, and then 'git add <file>'. When you do that, you'll get the warning saying that LF will be replaced by CRLF. Then you commit. The end result is that you have a workingdir with a mix of LF and CRLF files, which after some more operations may trigger a "whole file changed" diff, due to the workingdir file now having LF EOLs. An LF only conflict file results in the resolved file being in LF, the commit is in LF and a warning saying that LF will be replaced by CRLF, and the working dir ends up with a mix of CRLF and LF files. Signed-off-by: Marius Storm-Olsen <marius@trolltech.com> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin-merge-recursive.c')
0 files changed, 0 insertions, 0 deletions