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

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

>> What you are missing is that all people who need the build files
>> with LF line endings, need *all* text files with LF line endings.
>
> Which means that people using Tgit and MSVC (CRLF) are supposed to
> retrieve all their files including the autotool ones with CRLF, and
> cannot switch environments without a new pull (provided they set their
> options right).

Without a new checkout, yes.  A separate tree would certainly help in
keeping the user sane.

> Or people who use MinGW/cygwin must ensure they use LF always,

Yes, they should.  Nothing new there.

> even as
> the expectation is that gcc handles LF or CRLF sources transparently, so
> the only files that actually *need* to be LF are non .c/.h
>
> Do we expect to support a cygwin/MinGW gcc that can't handle CRLF?

Why does that matter?  GCC might handle CRLF line endings the way you
want; many other tools you can use with C files (grep, for one) don't.

> Again, why force-convert files if we don't have to?

Why play fast-and-loose with it if you don't have to?


Segher