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

[Segher B. <se...@ke...>]

>>> > People will need exactly those same settings for any other open
>>> source
>>> > project hosted in git,
>>>
>>> It's not because other people do one thing that we should follow suit,
>>> when we can fix a potential issue that they don't seem to either be
>>> aware of, or be willing to fix.
>
> I don't necessarily agree/disagree with Segher here on the whole.
> However,
> this whole "let's do what everyone else does" mindset is slightly
> annoying.

I recommend doing the same as all other projects do, since that is
_easier for all users_.

> Particularly since that eol attribute was only introduced in May, it
> seems.
> Maybe no one else has bothered to follow up on new features (having had
> this
> discussion when different features were available), or maybe no one else
> cares enough, or maybe no one else has the same priorities, or maybe they
> were using a different VCS and that affects things in some way.

Or maybe no one else considers this a problem?

>>> > Also, users who do not know this stuff are much more likely to use
>>> > tarballs / zipfiles anyway, as has been pointed out to you a lot of
>>> > times already.
>
> And this could be the snapshot solution.  LF in tarballs, CRLF in
> zipfiles.
> Slightly more work writing the script, but not too bad?

If we automate making release tarballs/zipfiles (and we should), it is
trivial to use the same thing for snapshots as well

> As discussed elsewhere with Segher, I'm not aware of a modern utility that
> fails to handle CONSISTENT line endings,

As I said there, and I'll say again: *ANY* unix program that doesn't
specifically handle CRLF, will not handle CRLF.  That is, most of them.

The consequences of that are benign in many cases.  They are not in
other cases.  That's the "autotools bug" as you guys call it.


Segher