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

Re: Retroactively adding versioned properties to files in a dumpfile

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Sun, 21 Sep 2008 19:07:13 -0500

On Sep 21, 2008, at 6:54 PM, Martin Furter wrote:

> On Sun, 21 Sep 2008, Ryan Schmidt wrote:
>
>> Anybody know how I can retroactively add properties to files? I'd
>> like to set svn:mime-type and svn:executable correctly for all my
>> files.
>>
>> I've used svndumptool.py [1] to clean up some other things in my
>> repository dump, but I'm not finding this feature. I find features
>> that are close:
>>
>> There's "svndumptool.py transform-prop" to change an existing
>> versioned property.
>> There's "svndumptool.py edit --propdel" to delete a versioned
>> property.
>> There's "svndumptool.py eolfix" to set or change the svn:eol-style
>> property and rewrite files' contents accordingly.
>>
>> What I'd sure like is "svndumptool.py set-prop" with which I could
>> set a property on files by regex, regardless of whether the
>> property was already set or not.
>>
>> Or maybe even better, a way for svndumptool.py to use the
>> autoprops section of my config file and rewrite history as if I'd
>> had that config file in place when adding every file.
>>
>>
>> [1] http://svn.borg.ch/svndumptool/
>
> Please try the new svndumptool command 'apply-autoprops'. I hope it
> does what you want (you need trunk).
>
> svndumptool.py apply-autoprops input.dmp output.dmp

Wow, that sounds great!

It's not mentioned in the README yet... Will this also handle eol
transformations, or do I need to separately use svndumptool.py eolfix?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-22 02:07:37 CEST

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.