{"thread":{"id":"31413","subject":"Suggested behavior when pulling .gitattributes","startedAt":"2012-09-01T23:21:51Z","lastAt":"2012-09-01T23:21:51Z","messageCount":1,"participants":["Aleksandr Dubinsky"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"198210","messageId":"CAEbpm93Pr8sU9mBx8V5VMmi5aXos-KBQpmEN7NPrdR07rYV5EQ@mail.gmail.com","threadId":"31413","inReplyTo":null,"subject":"Suggested behavior when pulling .gitattributes","fromName":"Aleksandr Dubinsky","fromEmail":"adubinsky@almson.net","sentAt":"2012-09-01T23:21:51Z","receivedAt":"2012-09-01T23:21:51Z","isPatch":false,"sender":{"key":"adubinsky@almson.net","avatar":null},"body":"Hi,\n\nI ran into a problem with line endings that .gitattributes is supposed\nto fix. However, I ran into a headache with this not giving the\ndesired result. This headache could have easily been avoided if:\n\nWhen pulling .gitattributes, git should parse the file and anything\nnew in it should be acted upon. Specifically, if a file already exists\nwith modified endings and .gitattributes now says it should be treated\nas binary, then please automatically re-checkout the file with the\ncorrect, un-modified line endings.\n\nPossibly this suggestion also applies to pushing/committing but that\nwasn't the problem I ran into just now.\n"}]}