Skip to contentSkip to conversation

Git improvement for line feed processing: LF versus CR-LF

DISCUSSION Francis ANDRE 2 participants 2 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi

I am using git-gui on a project hosted at GitHub and the project requirement is to commit only Unix ending with LF lines as show below

When contributing to POCO, please adhere to our coding style guide

All text file line endings in the repository must be Unix-style (LF). This includes Visual Studio project and solution files (.sln, .vcproj, .vcxproj, .vcxproj.filters).

But git-gui translates states:
warning: LF will be replaced by CRLF in file.txt. The file will have its original line endings in your working directory.

Could you add a option to git-gui to specify to translate or not the end of line of the cloned repository so that my fixes be accepted by the owner of the repository.

Thank

#1 lore raw
Quoted 10 lines · Francis ANDRE

Hi
[]
All text file line endings in the repository must be Unix-style (LF). This includes Visual Studio project and solution files (.sln, .vcproj, .vcxproj, .vcxproj.filters).

But git-gui translates states:
warning: LF will be replaced by CRLF in file.txt. The file will have its original line endings in your working directory.

Could you add a option to git-gui to specify to translate or not the end of line of the cloned repository so that my fixes be accepted by the owner of the repository.

Thanks

Unless I'm completely wrong, such an option already exists, please see

http://git-htmldocs.googlecode.com/git/gitattributes.html