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

Re: File/revision obliteration feature

From: <cmpilato_at_collab.net>
Date: 2002-08-23 17:30:58 CEST

Michael Price <mprice@atl.lmco.com> writes:

> 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.

It would certainly be my plan of attack in the absence of such a
command, yes.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 23 18:01:39 2002

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.