[prev in list] [next in list] [prev in thread] [next in thread] 

List:       subversion-issues
Subject:    =?UTF-8?B?W0lzc3VlIDUxNl0gIHN2biBvYmxpdGVyYXRl?=
From:       iaanus () tigris ! org
Date:       2007-03-08 17:16:59
Message-ID: 20070308171659.11266.qmail () tigris ! org
[Download RAW message or body]

http://subversion.tigris.org/issues/show_bug.cgi?id=516






------- Additional comments from iaanus@tigris.org Thu Mar  8 09:16:59 -0800 2007 -------
@Brian: if I understand it correctly, the task you describe can already and
easily be approached with a dump/filter/load cycle, as svndumpfilter is already
able to completely remove files and their *whole* history on a path basis. You
just need enough disk space to hold both the original and the "cleaned-up"
repositories during the cycle, but, after that, the original repo can be
deleted. The true use cases for obliterate are, IMHO, those described by
Stephanie and myself, where you need to remove just some revisions of a file,
leaving the file in the repository and *without* disrupting the working copies.

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org

[prev in list] [next in list] [prev in thread] [next in thread]