Lübbe Onken <l.onken@rac.de> writes:
> > What it does *not* document are
> > certain outright bugs in svndumpfilter that we weren't aware of until
> > today, and which I'm working to fix right now.
>
> Like getting copyfrom revision numbers off by one for example? I used
> --drop-empty-revisions and --renumber-revisions and ended up with
> results like:
*Exactly* like that. {grumble, mumble} But like I said, I'm working
on it.
> Second problem:
> We initially had a layout like:
> repos/trunk/ProjectA
> repos/trunk/ProjectB
> repos/trunk/ProjectC
> repos/tags/ProjectA_1.0
> which proved to be not-so-good :-)
>
> So in the early days of our repository I created the structure:
> repos/ProjectA/trunk
> repos/ProjectA/tags
> repos/ProjectA/branches
>
> for each project and moved the content of trunk/ProjectA to ProjectA/trunk
>
> After filtering out all the revisions that contained trunk/ProjectA
> and ProjectA/trunk, I ended with a complete revision history for
> ProjectA, but svnadmin was not able to import the dump file. Errors
> like non-existing paths were thrown at me. I had to manually edit the
> node-path for each revision before the restructuring took place. Maybe
> I used the wrong hammer, but these were my two major headaches.
Manual path tweaking is a common and currently unavoidable aspect of
this recipe. I've been thinking more about how to solve that, too.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 25 15:51:03 2004