git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
FAFrancis ANDRE <francis.andre.kampbell@orange.fr>
Date
Sep 8, 2014, 08:55 UTC
Message-ID
<540D6EEB.2040101@orange.fr>
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
Next: Torsten Bögershausen
Message 1 of 2 in “Git improvement for line feed processing: LF versus CR-LF”
  1. Francis ANDRESep 8, 2014
  2. Torsten BögershausenSep 8, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.