>> Let me illustrate. I want to change this kind of layout
>
>> so that it becomes:
>
>> svn/
>> foo/
>> trunk/
>> branches/
>> bar/
>> trunk/
>> branches/
>
> Shouldn't the following series of commands do the trick?
>
> svn mkdir http://server/svn/foo
> svn move http://server/svn/trunk/foo http://server/svn/foo/trunk
> svn move http://server/svn/branches/foo http://server/svn/foo/branches
Yep, that seems to do the trick ... except that I chose an overly simple
example :-)
I didn't mention how projects are spread out, renaming histories, and
stuff. Just an example:
svn_1/
trunk/
npm/
later became
svn_1/
trunk/
nepumuk/
which should now be fused with
svn_2/
trunk/
sunflower/
... with svn_2 having undergone many temporary trees due to a cvs2svn for a
subproject of sunflower. After loosing a few strands of hair over this I
noticed it boiled down to the reverse structure I had chosen at the
beginning, and that's what I based the example on.
The workaround I described in a previous post (moving things in a working
copy) is doing the trick for the current head revision, but if we ever need
to retrieve older things it will be complicated to take the layout changes
into account. I wanted to get this *right*, see?
I'm almost at the point where I'll write a custom script to modify the dump
files. That would be the cleanest solution. Does anyone have a dumpfile
tweaking script (preferrably Python) they'd feel like sharing with me? I
looked at the sources of svndumpfilter, but it seems like the effort needed
for understanding that goes beyond the amount I'm currently willing to
invest...
Thanks!
Rolo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 30 17:16:28 2004