Re: [Libusb-devel] CRLF in files checked out on Windows

[Peter S. <pe...@st...>]

Michael Plante wrote:
> >> Changing crlf settings in git never makes it change what is checked
> >> out.
..
> I'm not sure if I understand which "crlf settings in git" you're referring
> to:  those in .gitattributes or those in the git config?  If the latter, ok.

Both.


> But if the former, this cannot be true:
> 
> 
> >> Changing crlf settings in git never makes it change what is checked
> >> out.
> 
> As I mentioned, changing crlf settings in .gitattributes SOMETIMES
> changes what's checked out.

What *will be* checked out on the next git checkout command, yes.
The state of the worktree until that git checkout, no.

In particular changing the CRLF settings will influence what git
expects in the worktree, but not the contents of the worktree, which
is why lots of files can suddenly show up in git status, when playing
with the crlf settings.


> >> The commit identified by Michael introduces the eol attribute, and I
> >> prefer taking advantage of that rather than setting -text on the
> >> files
> 
> So would you say that that commit intentionally introduces the
> behavior I saw, or is the behavior I saw an unintended side effect?

I'm not sure exactly what happened in your worktree. :\ If you zip it
up I'll try to take a look when travelling this evening.


//Peter