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

Re: Copying (branch/tag), dumping, and filtering repository contents

From: Neil Martinsen-Burrell <nmb_at_wartburg.edu>
Date: 2007-09-14 06:30:15 CEST

Bicking, David (HHoldings, IT <David.Bicking <at> thehartford.com> writes:
> Alright, one more time, and then I give up. I though this would be a
> relatively simple question, but apparently I was wrong.

It is possible to filter out deeply-nested subdirectories from SVN repositories.
 It is not possible to do so using svndumpfilter however. It will fail (as you
may have noticed) on a revision that copies a file from an excluded path to an
included one. A (consistent if not ideal) solution is to mark such a copy as an
add of new content in the filtered repository. This is the approach taken by
Simon Tatham's svndumpfilter2
(www.tartarus.org/~simon-anonsvn/viewcvs.cgi/svn-tools/svndumpfilter2), Martin
Blais's svndumpfilter3
(http://furius.ca/pubcode/pub/conf/common/bin/svndumpfilter3.html) and my own
svndumpfilter4.py (https://www.undersea.com/~nburrell/svndumpfilter4). Simon's
is the root of all three of these possibilities, but they are all slightly
different in what they allow for exclusions and inclusions.

One might desire a solution that would keep the history of the file that was
copied from an excluded path, but then it would also have to keep the history of
any ancestors of the original, excluded file and so forth. This would result in
a filtered repository that could potentially include a great deal of stuff other
than the filtered paths. The above solution avoids that problem.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 14 06:27:18 2007

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.