> You probably still want the svndumpfilter processing to drop empty
> revisions before loading it in a new repository.
>
I believe that the current version of svndumpfilter only operates on
version 2 dump streams - which svnadmin dump produces. svnrdump
produces a version 3 dump stream and is not compatible with svnrdump.
That being said, I am able to get around dumping empty revisions (from a
previous dump/load) with svnrdump by running something along these lines:
for rev in `svn log -r0:HEAD ${url}/${project} | \
egrep "^r[0-9]+ |" | cut -d " " -f1`; do
svnrdump dump --incremental -r ${rev:1} ${url}/${project} >>
${project}.dump
done
Basically, I am only dumping (incrementally) the revisions which actually
affect the path in question. This obviously is not as fast as doing
everything
server-side, but it does appear to work around having files or directories
copied from paths outside of the particular project path. The
outside-copy-paths are dumped in full as opposed to just a simple reference
as to where it was originally copied from.
I would appreciate some feedback if I’m missing something or if the above
statement is inaccurate or unreliable. In my tests, everything appears to
be
the same once loaded into a fresh repository, checked out in full and
diffed
against the originals.
There is a very brief mention in the svn-book of appending to an existing
dump file, so I expect that to be safe in general. It can be found in the
“*Repository
Backup*<http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.backup>”
section by searching for ‘appending’.
Thanks,
Bryon Winger
