curl/.gitattributes

*.dsw -crlf
buildconf eol=lf
configure.ac eol=lf
*.m4 eol=lf
*.in eol=lf
*.am eol=lf
*.sh eol=lf
*.[ch] whitespace=tab-in-indent

# Batch files (bat,btm,cmd) must be run with CRLF line endings.
# Refer to https://github.com/curl/curl/pull/6442
*.bat text eol=crlf
*.btm text eol=crlf
*.cmd text eol=crlf
Add .gitattributes files to turn off CRLF translation for some files 2010-03-25 11:48:35 +08:00			`*.dsw -crlf`
Tell git to not convert configure-related files. 2012-07-16 00:25:55 +08:00			`buildconf eol=lf`
			`configure.ac eol=lf`
			`*.m4 eol=lf`
Tell git to not convert configure-related files. 2012-07-18 02:35:23 +08:00			`*.in eol=lf`
.gitattributes: turn off CRLF for *.am If Makefile.am uses CRLF, buildconf in a Windows checkout fails with: ".ibtoolize: error: AC_CONFIG_MACRO_DIRS([m4]) conflicts with ACLOCAL_AMFLAGS=-I m4" 2017-03-22 06:20:03 +08:00			`*.am eol=lf`
.gitattributes: force shell scripts to LF Bash on Linux errors out on CR characters. This makes tests 1221 and 1222 pass on Linux with a CRLF checkout. Ref: https://github.com/curl/curl/pull/1344#issuecomment-289243166 Closes https://github.com/curl/curl/pull/1422 2017-04-15 06:10:27 +08:00			`*.sh eol=lf`
.gitattributes: make tabs in indentation a visible error Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> 2018-12-07 03:20:32 +08:00			`*.[ch] whitespace=tab-in-indent`
gitattributes: Set batch files to CRLF line endings on checkout If a batch file is run without CRLF line endings (ie LF-only) then arbitrary behavior may occur. I consider that a bug in Windows, however the effects can be serious enough (eg unintended code executed) that we're fixing it in the repo by requiring CRLF line endings for batch files on checkout. Prior to this change the checked-out line endings of batch files were dependent on a user's git preferences. On Windows it is common for git users to have automatic CRLF conversion enabled (core.autocrlf true), but those users that don't would run into this behavior. For example a user has reported running the Visual Studio project generator batch file (projects/generate.bat) and it looped forever. Output showed that the Windows OS interpreter was occasionally jumping to arbitrary points in the batch file and executing commands. This resulted in unintended files being removed (a removal sequence called) and looping forever. Ref: https://serverfault.com/q/429594 Ref: https://stackoverflow.com/q/232651 Ref: https://www.dostips.com/forum/viewtopic.php?t=8988 Ref: https://git-scm.com/docs/gitattributes#_checking_out_and_checking_in Ref: https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration#_core_autocrlf Bug: https://github.com/curl/curl/discussions/6427 Reported-by: Ganesh Kamath Closes https://github.com/curl/curl/pull/6442 2021-01-13 15:03:57 +08:00
			`# Batch files (bat,btm,cmd) must be run with CRLF line endings.`
			`# Refer to https://github.com/curl/curl/pull/6442`
			`*.bat text eol=crlf`
			`*.btm text eol=crlf`
			`*.cmd text eol=crlf`