Re: special property for text types

On 2008-02-19 16:32:26 -0600, Travis P wrote:
> However, in an environment with many people having working directories on
> a non-local filesystem, such as AFS, the extra processing that is caused
> by line-ending-normalization is dramatic and horrid. And in our
> environment, it isn't adding anything because no one is access the repos
> on Windows.
>
> So, to save all users daily pain, I've removed the svn:eol-style from
> all the source files. All users use Un*x systems (AIX, Linux, MacOS X)
> to access the repository and I've added a hook script to ensure that no
> Windows-style line-endings make it into the repos by mistake.
>
> I need text files to continue to be recognized for line-based diff,
> merge, etc. without the stiff performance penalty triggered by setting
> svn:eol-style.

Why would it be a penalty when the line ending is the same in the
repository and on the platform (\n in both cases)? In such a case,
line-ending-normalization is a no-op, isn't it?

> (Caveat to my argument: I haven't tried adding svn:eol-style back
> recently to test if some advance was made in recent releases that might
> minimize the penalty. I believe the penalty was because Subversion was
> creating tmp files in the .svn/ directories in AFS working copies for
> every source file so it could normalize endings for comparison and other
> operations.)

If tmp files are necessary (and are really tmp files), shouldn't they
be created under /tmp for efficiency?

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org