From: Xiaofan C. <xia...@gm...> - 2010-12-06 14:19:00
|
On Mon, Dec 6, 2010 at 10:14 PM, Xiaofan Chen <xia...@gm...> wrote: > On Mon, Dec 6, 2010 at 9:33 PM, Xiaofan Chen <xia...@gm...> wrote: >> On Mon, Dec 6, 2010 at 9:27 PM, Pete Batard <pb...@gm...> wrote: >>> On 2010.12.06 13:05, Segher Boessenkool wrote: >>>> There isn't really any alternative; you cannot mix cygwin with >>>> "native" mswindows stuff, without issues like these. >>> >>> Yes you can if you commit files that should be CRLF/LF as CRLF/LF in the >>> repo in the first place and use binary mode (-crlf) always, which is my >>> proposal for official. >>> >>> There's aren't any files that I am aware of that would need to be CRLF >>> in cygwin and LF in native, or LF in cygwin and CRLF in native (unless >>> you consider that Notepad should be used to edit files that are meant to >>> be LF'd in the first place, like UNIX shell scripts. If despite the fact >>> that MS project files are text files, we agree that these should better >>> be CRLF'd, I don't see how we could fail to agree that despite the fact >>> that UNIX .sh or autotools .am/.ac are text files, they should be LF >>> always - especially as we've demonstrated 3 different issues with non >>> LF'd ones) >>> >> >> Yes this is well put. No conversion. And use the right tool >> to edit the text files -- do not use Notepad to edit shell >> script or use Unix editor to edit CRLF text files. >> > > That being said, I do not see any files need to be forced > to be CRLF, With perhaps the exceptions of the MSVC project files. But if we tread them as binary files, then there are no problems. > even the text files (the two files with .txt > extension from libusb-pbatard). The are not CRLF > in my checkout so it is not good to use Notepad > to view it. Is that a problem? Not a problem for me. Since I use Notepad++ under Windows, > With this, then the maintainers who do not > use Windows can edit those text files > as well. > -- Xiaofan |