On Fri, 2004-04-30 at 08:40, Jim Fulton wrote:
> Often when someone checks in a binary file, they forget to mark it as such.
> This is easy to fix, once it is detected, although, it isn't always detected as
> soon as one would expect. You suggest that adding files is rare.
> For most projects, including ours, the great majority of files are text, so
> problems with failing to mark binary files are very rare. Line endings for
> text files is just not an issue.
Interesting philosophical extremes here. CVS is one extreme, SVN is
other.
CVS assumes all files are text by default, and assumes it can munge your
line endings by default. Somebody checks in a binary file and forgets
to use '-kb', and bam, the file is corrupted. There's no easy way to
recover from that corruption.
The SVN reaction to that was to move to the other end of the scale:
*never* change file contents unless explicitly given permission. If
somebody forgets to activate eol-translation on a file, it's not a big
deal. Somebody loads a file into an editor, sees unreadable line
endings, then sets the property to fix the problem. No data loss. But
overall, yes, there's some general convenience sacrificed here, since
people need to set the eol-translation on every new file.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 30 18:07:56 2004