On Mon, 2001-12-03 at 22:18, cmpilato@collab.net wrote:
> 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?
It is very easy to avoid destroying data. You stick to the following
rule: never apply transformations on the commited data; do apply
transformations on checkout, and to files in the working directory after
a commit.
CVS follows this rule for keyword substitution; you can always check out
a revision -ko to see what keyword strings were in the file at the time
of commit. (However, it doesn't treat the default keyword substitution
as a historical property, which can suck sometimes.) I don't honestly
know if CVS follows the rule for newline translations.
Of course, the rule only gives you a fallback position, and many users
are not sophisticated enough to know that the un-transformed data is
still there or how to get it. But for those paranoid about losing data,
perhaps it can provide some measure of comfort.
---------------------------------------------------------------------
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