Re: File/revision obliteration feature

cmpilato@collab.net writes:
> If the file is originally at /trunk/notes/private.txt, and you do a
> few branches and tags, a clean obliteration means hunting down not
> just all version of private.txt, but all versions of all branches of
> private.txt, *and* all nodes in all revisions that point to
> private.txt as a child entry. Because filesystem nodes don't keep
> pointers to their (potentially multiple) parent nodes, finding those
> parent nodes could cost you dearly. To quite gstein: "Cheers!"

Yeh, that is a messy problem.

So assuming you discover the "accident" quickly (i.e. it occurred a few
revisions ago) then your best bet to solving the problem is to:

  1. make a dump of everything up to the revision before the "accident"
  2. make a few diffs and notes for the remaining revisions
  3. load the dump into a new repository
  4. recommit the appropriate bits/copies/merges/etc

Messy but faster than writing an obliteration command.

Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 23 17:54:27 2002