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

Re: So which is subversion wrong about; changing imported files

From: Jeff Smith <jsmith_at_robotronics.com>
Date: 2007-03-07 01:28:25 CET

On Friday 02 March 2007 20:31, Ryan Schmidt wrote:
> AI think I agree: Subversion has modified the file. However I think
> that by using the svn:eol-style property, you have asked
> Subversion to modify the file. I'm not sure how the feature could
> otherwise function.

[ On a sidenote; that being an option was exactly my point, when
certain people disagreed strongly whether there should be an
__OPTION__ (...just making sure certain people notice that word...)
to allow svn:eol-style to also accept a file with mixed eol-styles.
I'm glad you understand, but that was not what I wanted to discus
right now...

So now I get the idea that subversion would have had a better start by
not allowing an immediate "eol-style solution" on import. Instead, it
should always import the initial rev as-is. Then for a convenient
auto-props feature, it should make a _next_ revision with useful
modifications such as normalization--or perhaps only translate eol
(according to svn:eol-style) as files leave the repository, although
perhaps internal normalizing is done for speed or simplicity.

An example is almost demonstrated in the comment that mixed eol-styles
are "handled" when the vendor releases (imported without auto-props)
are merged into a tree in the trunk which already has desired files
set with svn:eol-style. The problem is, how to I get them all
automatically set without being able to use auto-props?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 7 01:29:07 2007

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.