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

RE: suggestion for improved docs on autocrlf

From
YMYagnatinsky, Mark <mark.yagnatinsky@bofa.com>
Date
Aug 12, 2019, 18:00 UTC
Message-ID
<aae529ce1b084b7bbcca3977e6909417@bofa.com>
In-Reply-To
<20190812171049.ydec3nsmkt2xplhd@tb-raspi4>

Okay, I feel like I'm on the verge of understanding, but it keeps eluding me, because you keep answering the question I actually asked, rather than the one I should have asked... let me try again, and bear with me if it seems like I'm repeating the same question over and over, because I don't understand which "irrelevant" differences matter and which don't. (You've been amazingly patient so far actually. Thank you for that.)

(Incidentally, you've successfully convinced me that attributes are a far better way to deal with this. I still feel that the behavior should be documented though.)

Setup: Suppose there exists a repo where sample.txt has CRLF line endings.
Meanwhile, my git config has autocrlf as "input".  Now, I clone the repo.
I edit sample.txt, and then commit.  Assuming the repo has no .gitattributes,
is it possible to predict what line endings sample.txt will end up with in my repo?
Or does it depend on more information than what I've just written?

---------------------------------------------------------------------- This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message.

Previous: Torsten BögershausenNext: Junio C Hamano
Message 12 of 23 in “suggestion for improved docs on autocrlf”
  1. Yagnatinsky, MarkAug 7, 2019
  2. Torsten BögershausenAug 8, 2019
  3. Yagnatinsky, MarkAug 8, 2019
  4. Yagnatinsky, MarkAug 8, 2019
  5. Torsten BögershausenAug 9, 2019
  6. Yagnatinsky, MarkAug 9, 2019
  7. Torsten BögershausenAug 11, 2019
  8. Yagnatinsky, MarkAug 12, 2019
  9. Junio C HamanoAug 12, 2019
  10. Yagnatinsky, MarkAug 12, 2019
  11. Torsten BögershausenAug 12, 2019
  12. Yagnatinsky, MarkAug 12, 2019
  13. Junio C HamanoAug 12, 2019
  14. Yagnatinsky, MarkAug 12, 2019
  15. Torsten BögershausenAug 13, 2019
  16. Yagnatinsky, MarkAug 13, 2019
  17. Torsten BögershausenAug 13, 2019
  18. Yagnatinsky, MarkAug 13, 2019
  19. Yagnatinsky, MarkAug 14, 2019
  20. Yagnatinsky, MarkAug 15, 2019
  21. Torsten BögershausenAug 16, 2019
  22. Yagnatinsky, MarkAug 16, 2019
  23. Junio C HamanoAug 13, 2019

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.