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

[Michael P. <mic...@gm...>]

Pete Batard wrote:
>> On 2010.12.07 12:39, Michael Plante wrote:
>> > And this could be the snapshot solution.  LF in tarballs, CRLF in
zipfiles.
>> > Slightly more work writing the script, but not too bad?
>>
>> What do you mean? MS projects being LF in tarballs?

No, source and docs LF in tarballs, CRLF in zipfiles.  Everything else is, I
think, agreed on:  sh/ac/am always LF in both, ds?/vcproj/sln always CRLF in
both.


>> Yeah. I can't say that I am confident that I didn't screw up these tests
>> somehow. But my line of thinking is that if I managed to screw up eol=lf
>> conversion, even if it was due to very specific conditions, then someone
>> else can do so.

Yes, but I have no reason to be confident that -text works, either.



>> Just tested grep, more (less), vim, and a few other command line tools
>> in cygwin and MinGW, and at least for the versions I have, they are CRLF
>> aware.

Yes, the grep test Segher proposed does work in the version of grep I have
in Windows.  It just doesn't work in Linux.  I hadn't thought to test that.


>> Provided [...]
>> the results I experienced in July when using "eol=lf" were just a fluke.

Now I'm curious whether you were using a version of git that was at least as
new as May 19th, plus however long it takes msys to package it.


Segher Boessenkool wrote:
>> >> 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.

Ah, Pete, tell me if this would help:

1. put two trees on your Linux box, one with autocrlf=false locally, and one
with it true.

2. Set the one with autocrlf=false to pull from the one with it true.

3. Copy files between the one with autocrlf=true and Windows.

Would that help you out?  I think that *avoids* the need to have filesystems
visible one way or the other (SMB, NFS, etc), unlike the other option I
suggested.



Michael