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

Suggested behavior when pulling .gitattributes

From
ADAleksandr Dubinsky <adubinsky@almson.net>
Date
Sep 1, 2012, 23:21 UTC
Message-ID
<CAEbpm93Pr8sU9mBx8V5VMmi5aXos-KBQpmEN7NPrdR07rYV5EQ@mail.gmail.com>
Hi,

I ran into a problem with line endings that .gitattributes is supposed to fix. However, I ran into a headache with this not giving the desired result. This headache could have easily been avoided if:

When pulling .gitattributes, git should parse the file and anything new in it should be acted upon. Specifically, if a file already exists with modified endings and .gitattributes now says it should be treated as binary, then please automatically re-checkout the file with the correct, un-modified line endings.

Possibly this suggestion also applies to pushing/committing but that wasn't the problem I ran into just now.

Message 1 of 1 in “Suggested behavior when pulling .gitattributes”
  1. Aleksandr DubinskySep 1, 2012

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.