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

On Mar 6, 2007, at 18:28, Jeff Smith wrote:

> 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?

You're saying: you have imported a tree without using auto-props, and
now would like to apply properties globally to what's already in the
repository? I think that's what the svn_apply_autoprops.py script in
the Subversion source distribution is for:

http://svn.collab.net/viewvc/svn/tags/1.4.3/contrib/client-side/
svn_apply_autoprops.py?view=markup

There's also another version of this script written by Matthew Good
which is supposed to have better performance and also SVK compatibility:

http://matt-good.net/2005/12/23/new-and-improved-svn-apply-autoprops-
py-now-with-more-svk/

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org