On Fri, Feb 12, 2010 at 5:16 PM, Bob Archer <bob.arc...@amsi.com> wrote: > Ah I see. Then wouldn't he just specify svn:eol-style CRLF? Assuming he only > every edits with Windows tools.
This isn't Windows-only code, and it's not code that only I'm touching. If someone's checking it out in Linux to compile in Linux normally, then it should have Unix line endings as usual. > Although I'm not sure why he wouldn't check out with a windows client. I'm > not sure how connecting to a Linux machine to checkout to a folder mounted on > a windows machine is easier than using the windows CLI. It's easier because it's a fully configured CLI that I already have running all the time, which does everything the way I want. I don't want to have to do half of my CLI work from a clumsy Cygwin window, especially since I have working copies in both Linux and Windows that I deal with simultaneously. > Instead, we set svn:eol-style to LF, and configured our Windows editors to > know how to deal with such files. Visual Studio just doesn't understand it. It'll load them and do basic editing fine, but copy/paste leads to mixed newlines. -- Glenn Maynard
