Re: Issues 516: "svn obliterate"

[Vlad Skvortsov <vs...@73rus.com>]

Garrett Rooney wrote:

>>
>> I would like to bring up slightly different topic here, though.
>> Dump/filter/load cycle can help with getting rid of specific commit, but
>> another issue here is references. Commit log messages often contain
>> references to prior commits - in form of "merged r1234:1239 from /a/b/c"
>> or "follow-up to r1234", etc. It's invaluable piece of information for
>> any nontrivial project and in my opinion it would be great if the
>> proposed procedure was able to keep revision numbering intact (just
>> "blacking out" specific commits).
>
>
> That can be done today (and would be in such a situation), simply
> insert empty revisions in place of dropped ones.  I believe
> svndumpfilter already has support for such a thing.  Yep, the default
> behavior for svndumpfilter exclude is to leave empty revs, you have to
> use --drop-empty-revs to make it leave out a rev even if there are no
> changes left in it.

Oh, thanks for the pointer - I have overlooked that.

-- 
Vlad Skvortsov, vss@73rus.com, http://vss.73rus.com

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