Hi, Les, Von: Les Mikesell [mailto:[email protected]] > > 2011/9/7 Thorsten Schöning <[email protected]>: > > > >> Would it work to start the dump at the revision of the move to the > >> current path (without --incremental) if I'm willing to lose the older > >> history that might have been in a cvs conversion? > > > > Is space a problem or why do you not just dump and load the whole > > repository and delete every path you don't need using svn? It may be > > the fastest solution and really preserves all history. > > There are currently a large number of projects in one repository. The size > is still manageable but approaching being awkward to back up and > manipulate. The point of splitting would be make the size for each > project reasonable - or perhaps to split out a project to be managed by a > group that should not have access to some of the other parts. > From the docs I would have expected giving a starting revision to svnadmin > dump to eliminate the history - and need for paths containing it - before > the specified point. Is that not the case?
I did not follow the thread, but did you have a look at svndumpfilter? http://svnbook.red-bean.com/en/1.6/svn.reposadmin.maint.html#svn.reposadmin.maint.filtering Best regards Markus Schaber ___________________________ We software Automation. 3S-Smart Software Solutions GmbH Markus Schaber | Developer Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50 Email: [email protected] | Web: http://www.3s-software.com CoDeSys internet forum: http://forum.3s-software.com Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
