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

The different EOL behavior between libgit2-based software and official Git

From
Yue Lin Ho <yuelinho777@gmail.com>
Date
Jun 19, 2014, 02:59 UTC
Message-ID
<1403146778624-7613670.post@n2.nabble.com>
Hi:
^_^

I did some test on the EOL behavior between official git and libgit2-based software(TortoiseGit). Then, I got that they have different EOL behavior.

The blob stored in repository is a text file with mixed EOLs. Even set core.autocrlf = true, official git checkout the file as it is(means still *mixed EOLs* there). But, libgit2 checkout it with *All CRLF EOLs*.

 * The steps:
   * set core.autocrlf = false
   * add file with mixed EOLs
   * set core.autocrlf = true
   * delete that file in the working tree
   * checkout that file
   * examine the EOL

If you are interested in this, you might take a look at my testing repository on GitHub. (https://github.com/YueLinHo/TestAutoCrlf)

Thank you.
Yue Lin Ho

-- View this message in context: http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software-and-official-Git-tp7613670.html Sent from the git mailing list archive at Nabble.com.

Next: Torsten Bögershausen
Message 1 of 10 in “The different EOL behavior between libgit2-based software and official Git”
  1. Yue Lin HoJun 19, 2014
  2. Torsten BögershausenJun 19, 2014
  3. Yue Lin HoJun 19, 2014
  4. Torsten BögershausenJun 20, 2014
  5. Yue Lin HoJun 20, 2014
  6. Torsten BögershausenJun 20, 2014
  7. Junio C HamanoJun 20, 2014
  8. Torsten BögershausenJun 22, 2014
  9. Junio C HamanoJun 23, 2014
  10. Yue Lin HoJun 20, 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.