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

Re: svnsquash has grown new capabilities

From: Martin Furter <mf_at_rola.ch>
Date: Sat, 10 Oct 2009 16:23:21 +0200 (CEST)

On Wed, 7 Oct 2009, Blair Zajac wrote:

> Martin Furter wrote:
>> On Wed, 7 Oct 2009, Blair Zajac wrote:
>>
>>> The one I've needed is when you're pulling a project out of a larger
>>> repository
>>> into a new smaller one, so you want to the project up one or more
>>> directory levels.
>>>
>>> For example, project foobar has a directory foobar in the repository
>>>
>>> foobar/
>>> trunk/
>>> tags/
>>> branches/
>>>
>>> and you want a new foobar repos with just trunk, tags and branches at the
>>> top
>>> level. So svndumpfilter works for pulling foobar, but not for moving it
>>> up.
>>
>> The 'merge' command of svndumptool can do that, and it's perfectly fine to
>> merge only one dumpfile.
>>
>> svndumptool.py merge -i in.dmp -x foobar -r foobar/trunk trunk ... -o
>> out.dmp
>
> I did install svndumptool before editing my dump file by hand to see if it
> had this functionality but didn't see an appropriate subcommand.
>
> Maybe there could be an additional subcommand for doing this? Or perhaps
> 'svndumptool help' would show it.

Yes, merge should be split into multiple commands. Implementing the squash
command of svncutter could already use some code which is hidden in merge.

Improving the help output is also on the todo list...

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2405874
Received on 2009-10-10 16:22:32 CEST

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