Garrett Rooney wrote:
> Justin Hahn wrote:
>
>> Perforce has a very handy way of doing this: the "obliterate" command
>> (which requires admin access to the repository, and a bunch of other
>> safeguards.) Is there an equivalent function in svnadmin or the svn?
>> While I can probably live without it, this functionality has been
>> quite valuable on a couple occasions. (You checked in how many gigs?
>> Why the hell? etc.) Even with CVS, if you really new what you were
>> doing, you could pull this off with rm and some editing.
>>
>> The only thing I could find in the archives was a short thread from
>> about a year ago suggesting this was to be implemented.
>
>
>
> well, nobody's saying that we shouldn't have this feature, but due to
> the fact that the file system is designed specifically /not/ to ever
> lose data, it's not exactly a simple change. what you're asking for
> will most likely be implemented post 1.0 as a result.
It is, in fact, planned for after 1.0; see
http://subversion.tigris.org/issues/show_bug.cgi?id=516.
> that said, if you're willing to get intimately familiar with our dump
> format, you could likely manage to dump the repository, restore
> everything from before the stuff you don't want went in, then
> selectively add in revisions after that point excluding the parts that
> involve the stuff you're trying to get rid of. i'm not positive this
> would work, but i suspect it would, although it would likely not be
> much fun to do.
The easiest way would be to just edit the dump file, removing all
references to the "obliterated" data. It's not exactly the easiest thing
in the world, but it should be possible, but note the warnings in the issue.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 7 16:29:09 2003