On Tue, 2003-12-30 at 14:38, Sidney Markowitz wrote: > Duncan Findlay wrote: > > I'm not really sure if that's what we ought to do > > I share your ambivalence. It's clear that it makes no difference on > unix/linux systems, since the native format would be the same as the > status quo. It doesn't seem to make a difference in Windows if you are > using Visual C++ 6.0 or later, ActivePerl, and nmake as your build > tools. They recognize unix newlines with no problem.
Recognise yes, honor no. IOW, once you save a file in VS it gets \r\n line endings. > I started to type here the scenarios in which there could be problems, > and I realized that they are all too farfetched to worry about. All that > is comes down to is that if any developer with commit rights is running > Windows, they should be careful to make sure that newlines come out > right if they create and submit a new file, and not do anything stupid > that would have the effect of causing a newline conversion of any file > that they edit and then commit. I'm on both linux and win32. I can tell you from experience that this problem will show up. What happens is that you get a diff comprised of the entire file (since each line changed). Very hard to spot the real diff in that. Why put the burden of making sure this doesn't happen on the developer when there is a perfectly good tool to prevent it? > So I guess this ought to be in the category of "ain't broke, don't fix it." Please consider setting svn:eol-style native on all source files. Sander
