On Wed, 2003-12-31 at 18:42, John Szakmeister wrote:
> The reason was frightening was the Subversion is more binary friendly, and if
> for some reason a binary file is added to the repository with the eol-style
> got applied, then we'd have a corrupt binary file in the repository.
I had initially advocated committing all files as-is, to avoid any
possibility of binary corruption, so that the repository representation
of text files might flop back and forth between LF and CRLF as commits
were done on Unix or Windows, but of course the client would make them
consistent.
That didn't take, but as a compromise, we refuse to perform
data-destroying translation on files with an svn:eol-style of "native".
We error out rather than convert a file with mixed line-endings.
But for the fixed eol-styles, we assume those are only going to be used
in very special cases, like MSVC project files, so the chances of them
being accidentally applied to a binary file are low. Also, files like
that are more likely to get mixed newlines when edited on platforms
whose native newline style doesn't match the fixed style. So, for those
newline styles, we do perform potentially data-destroying
transformations on commit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 1 02:00:52 2004