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

Re: Faking obliteration

From: Alexander Sabourenkov <screwdriver_at_lxnt.info>
Date: 2003-07-17 10:31:41 CEST

Martin v. L÷wis wrote:
> Ben Collins-Sussman <sussman@collab.net> writes:
>
>
>>For now, all you can do is dump and load. Use svndumpfilter to
>>'screen out' the bad path when you're reloading.
>
>
> That sounds very promising, thanks!
>
> Is it true that svndumpfilter is nowhere documented?
>

Well.. `svndumpfilter help` is the only docs I'm aware of. You should also
make yourself familiar with the dumpfile format so as to understand what
exactly you're doing. Read notes/fs_dumprestore.txt in the source.

Also read this thread:
http://www.contactor.se/~dast/svn/archive-2003-03/1520.shtml

The svndumpfilter usage is pretty simple - to filter out some file or
directory from repository you only need exact path where it was first committed.

Then you do svnadmin dump repos | svndumpfilter exclude path/to/ >newdump.

Then you load newdump into a separate repo and triple-check that it's ok.

This can get pretty complicated if you moved the file around the repo, then
later created other file with the same path in repo, etc, etc.

Svndumpfilter will catch copies of the file, but i think it will also catch
unrelated file with the same name in a later revision.

In this case you'll have to separately svnadmin dump and filter several
revision ranges.

-- 
./lxnt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 17 10:32:43 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.