threads / discuss / 31413

Suggested behavior when pulling .gitattributes

Subject: Suggested behavior when pulling .gitattributes

## tl;dr

One message between Sep 1, 2012 and Sep 1, 2012.

replies: 0people: 1as markdown or json

Aleksandr Dubinsky· Sep 1, 2012, 23:21 UTC · lore
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.

← back to recent threads