[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Auto-prop not working?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-04-22 20:05:40 CEST

On Apr 22, 2005, at 12:51 PM, Peter McNab wrote:

> So If at some stage I start putting keywords into text files and
> enable keyword expansion or whatever the term is, then there is a
> chance maybe a spreadsheet or text document with the same string might
> become corrupted?

Sure, if you set the svn:keywords or svn:eol-style property on a file,
you're giving svn permission to start munging the contents of the file
by looking for patterns of data to substitute. It's obviously not a
good idea to allow such a thing on a binary file.

> I currently don't distinguish between binaries and text when
> committing from the GUI, like we did in CVS.

With subversion, you can relax. It assumes all file contents are
sacred by default, and will *only* munge contents if you set those
special properties. CVS is the opposite; it assumes all files are
mungable text, and you have to explicitly tell it not to munge data (by
setting the '-kb' flags on a file.)

> What is the correct approach "currently" to absolutely avoid the
> potential for corruption?

Don't set svn:keywords or svn:eol-style on any file, ever. :-)

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 22 20:09:17 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.