Billy Tanksley <btanksley@hifn.com> writes:
> I'm still very nervous on newline conversion. Will it be possible to
> configure svn to not, by default, destroy any and every binary file checked
> into it?
Subversion already include a heuristic for determining whether or not
a file is "binary" at import and add times. The value can, of course,
be overridden. Default behavior for binary files should, therefore,
be to NOT do newline conversion.
> My preference would be to leave this feature completely out of svn,
> and provide a command-line utility. I've done a lot of
> cross-platform development, and I've never once been glad to have
> newline conversion be done for me (every editor I use can do that
> itself). OTOH, in every cross-platform project I've ever worked in
> there's been at least one file destroyed by CVS' conversion.
Honestly, I have the same preference. In fact, my preferences
regarding what I wish Subversion would do (or more specifically, not
do) extend beyond that, and can be basically summed up by: Subversion
should version file contents and user properties. That means no
versioning of file permissions, no newline conversion, no keyword
substitution.
Alas, I have a feeling I'd be strongly outvoted on many (all?) of
these points, though, and ultimately, I want Subversion to rock CVS'
world. So I code on...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:51 2006