Le 26/06/2016 18:08, Georg Baum a écrit :
Scott Kostyshak wrote:
I think this is due to the recent fixes in .gitattributes. In any case,
git reset --hard does not fix anything. But the following does work for
me:
Yes, this was caused by the introduction of .gitattributes, since these
files were checked in with windows line ends before, but were now treated as
text files with unix line ends on unix workspaces. Funnily I never saw that
myself, but it should be fixed at 933bc7f0ddf. PLease tell me if you ever
see this again.
I just saw this when checking out a commit after your fix, and then back
to a commit before it. The trick mentioned by Scott worked.
