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

Re: Publishing part of a repository

From: Robin Becker <robin_at_reportlab.com>
Date: 2004-07-03 14:22:38 CEST

Branko Čibej wrote:
> Robin Becker wrote:
>> Is this sort of thing feasible? I was planning to do this with a
>> python script & regexes, but see that there is a python binding to the
>> libs. Unfortunately I don't seem to find a good description of the
>> library api. (I'm probably looking in the wrong place).
> For this kind of change, you'd do better to write a python script that
> work directly on dumpfiles. The dump format is very easy to parse. I'd
> suggest dumping both repositories, then reading both at the same time
> and generating a merged dumpfile with the paths renamed. The renaming
> should be easy (basically string.replace, you don't even need regexes),
> and the sorting is a simple merge of the files, since the revisions in
> each one are already sorted by date.
> What you _do_ have to be careful about is how you map revision numbers
> -- each of the old repos will have a different mapping. When you load
> the resulting dumpfile, I suggest you do so with the --ignore-uuid
> option, because you don't want people to accidentally try to update
> their old working copies from the new repos -- that won't work.
> -- Brane

well if I could find a definition of the format I would be happier. I'm
sort of planning on what you suggest, but I was going to renumber the
revisions as the merge takes place. The --ignore-uuid thing is obviously
the right way to do things. I probably have to be careful with not doing
things twice eg I will now have two trunk adds under my proposed
renaming so I guess I need to ignore one or the other.

Robin Becker
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Jul 3 14:23:09 2004

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.