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

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

Pete Batard wrote:
> * eol=lf / eol=crlf and running the risk of having it overridden and 
> people not getting lf'd files if they use MSYSgit

I have always written: text eol=lf

That's two attributes. I'm sorry if I should have pointed that out
more explicitly - I thought I had already made it clear.

Without text in .gitattributes there are certainly many settings that
influence git conversion, but text eol=lf is unambiguous.


> > users who do not know this stuff are much more likely to use
> > tarballs / zipfiles anyway,
> 
> Then you are discriminating.

We speak from (in case of Segher, significant) experience. It's not a
rule, but it is the common case, thus what we should optimize for.


> So far, the only reasons for rejecting -crlf I have seen are:
> - *you* don't want CR in the repo
> - *you* don't want to constrain LF, even as we know that we want LF
> on some files always, as it avoids issues.

Allow me to repeat my argument: (for the fourth time, is it?)

The files are text, so they should be marked as such.

(And for some reason you also keep ignoring that crlf is only a
compatibility name, so we should talk only about text vs. -text,
not crlf vs. -crlf.)

You may understand that it is becoming difficult to discuss this
further, when me repeating and trying to clarify myself clearly
does not work. :\


> no matter what Peter says, I do NOT trust eol=lf to solve our
> problem,

With or without text? As I tried to show, without text eol is not of
much use at all, and with text it becomes unambiguous.


> Maybe Peter is confident in git's line conversion, but, from
> experience, I'm not,

Maybe it was just configured wrong. There are a fair number of
settings to take into account, and it certainly took me several
readings of documentation, and some testing, to get a grip on git
in this respect. Maybe spent half an hour on it. Followed by a few
days of your FUD. Please test, and certainly let us know if there
is an actual problem with what I suggested.


//Peter