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

Re: svnadmin obliterate features (was: RE: the obliterate discussion - why dumpfiltering is no validworkaround)

From: patrick <Patrick.Wyss_at_mobilesolutions.ch>
Date: 2007-07-23 17:26:43 CEST

Cem Karan wrote:
>
> OK, what features are needed for this?
>
> Reading through the messages, I see the following requests
>
> 1) (Obviously) Completely erase a file/directory & its history from a
> repository
> 2) Make this non-blocking.
> 3) Add in regex support to select which files/directories to wipe out.
>
that was my proposal, yes...

>
> I want to modify #1; instead of wiping out a file/directory completely,
> I would like to be able to specify a revision range. Here is the case
> I'm thinking of:
>
>
...

> svnadmin obliterate -r 123:145 myFile
>
> Other command forms would look like:
>
> svnadmin obliterate [-r M:N] sourceURL // Wipe out a specified range
> svnadmin obliterate [-r :N] sourceURL // Wipe out everything up to
> version N
> svnadmin obliterate [-r M:] sourceURL // Wipe out everything starting
> from version M through the most current
> svnadmin obliterate [-r M] sourceURL // Wipe out version M
>
>
deleting a single revision makes it necessary to recalculate the delta for
the version before or after (AFAIK DB and FSFS do deltas in opposite
direction)
deleting whole ranges makes it necessary to "sum up" these deltas.

i recon that the delta algorithm is already implemented so i guess it does
not make the task a lot more difficult. (how about performance?).

i can see the need for this function but IMO one could start with the real
simple solution and have this added in a second iteration.

>
> As for #2, I'm not sure if that is possible (although it would really be
> nice if it could be done). As long as the amount of time spent block is
> relatively short regardless of the version range/directory size being
> obliterated, it shouldn't be that big a deal.
>
>
i agree on this. actually this was what i had in mind

>
> Finally, #3 will likely just take away effort from the real work. I
> know that I tend to use the find command to find the exact files I want,
> and then run commands on just those files. I suspect that working on
> regex support for obliterate will take away time that would be better
> spent on getting it working.
>
i agree with this. "make it as simple as possible" is what i said in the
first place and you are right, there are other solutions for solving this.

-- 
View this message in context: http://www.nabble.com/the-obliterate-discussion---why-dumpfiltering-is-no-valid-workaround-tf4116918.html#a11746747
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 23 17:25:48 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.