Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
> Hi,
>
> modifying a .cxx file on Windows, and committing it to SVN, followed by
> a "svn diff -r PREV <file>", shows me that *the complete* file changed
> with the commit. Doing a "svn diff -r PREV -x --ignore-eol-style <file>"
> shows me only the changes which I just did.
>
> Conclusion: We have a problem with our line endings - we certainly do
> *not* want to have a thousands-line-change-set for every file we
> modify/commit on Windows, do we?
>
> Shouldn't we set to svn:eol-style property to a reasonable value
> ("native", probably) for all our source files, globally?
Will also not really help in all cases. If you check out under Unix (or
cygwin) and commit on Windows you get the same problem, which is
probably a common scenario. Unfortunately not everyone uses an able
editor which detects the line-style and conserves it on Windows. I've
thought a while about setting eol-style "native" during the migration,
but the best practices recommended to not set a eol-style to prevent
garbling of not correctly flagged binaries (I'm sure we've got a few).
This doesn't prevent us to do it now, of course. We would need to
prepare a list of files types which we consider sources ...
Let me hear your thoughts. Should we go to svn:eol-style native? For
which file types? Or should we stay with Unix and require that people
use editors which preserve the line end conventions? Is that even
possible for the more popular editors (I use vim, so I wouldn't know).
Heiner
--
Jens-Heiner Rechtien
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
