diff options
author | Torsten Bögershausen <tboegi@web.de> | 2014-06-29 08:34:54 +0200 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2014-07-08 12:40:40 -0700 |
commit | 343151dcbdf63a4f12b1a0108708280dc3883af6 (patch) | |
tree | 43192d646789494a459c25b9b0f279d6333dee1a /t/t3300-funny-names.sh | |
parent | t0025: rename the test files (diff) | |
download | tgif-343151dcbdf63a4f12b1a0108708280dc3883af6.tar.xz |
t0027: combinations of core.autocrlf, core.eol and text
Historically there are 3 different parameters controlling how line endings
are handled by Git:
- core.autocrlf
- core.eol
- the "text" attribute in .gitattributes
There are different types of content:
- (1) Files with only LF
- (2) Files with only CRLF
- (3) Files with mixed LF and CRLF
- (4) Files with LF and/or CRLF with CR not followed by LF
- (5) Files which are binary (e.g. have NUL bytes)
Recently the question came up, how files with mixed EOLs are handled by Git
(and libgit2) when they are checked out and core.autocrlf=true.
See
http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software-and-official-Git-td7613670.html#a7613801
Add the EXPENSIVE t0027-auto-crlf.sh to test all combination of files
and parameters for both "git add/commit" and "git checkout".
Signed-off-by: Torsten Bögershausen <tboegi@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3300-funny-names.sh')
0 files changed, 0 insertions, 0 deletions