Hi James!
> repo:
> /
> /projectA/subcon/component1
> /projectA/subcon/component1/branches
> /projectA/subcon/component1/tags
> /projectA/subcon/component2
> /projectA/subcon/component2/branches
> /projectA/subcon/component2/tags
> /projectA/subcon/component3
> /project/B
> # svndumpfilter exclude project/A/component3 < original_dump > without3_dump
Is this just a typo here? In the above repo layout I don't see
"project/A/component3".
So should it not have been
# svndumpfilter exclude projectA/subcon/component3 < original_dump > without3_dump
?
Other than that, here a quote from the svn book:
---------------- snip -----------------
While svndumpfilter can be very useful, and a huge timesaver, there
are unfortunately a couple of gotchas. First, this utility is overly
sensitive to path semantics. Pay attention to whether paths in your
dump file are specified with or without leading slashes. You'll want
to look at the Node-path and Node-copyfrom-path headers.
…
Node-path: spreadsheet/Makefile
…
If the paths have leading slashes, you should include leading slashes
in the paths you pass to svndumpfilter include and svndumpfilter
exclude (and if they don't, you shouldn't). Further, if your dump file
has an inconsistent usage of leading slashes for some reason, you
should probably normalize those paths so they all have, or lack,
leading slashes.
---------------- snip -----------------
Cheers, Ingo =;->
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 30 19:14:55 2007