[
https://issues.apache.org/jira/browse/SVN-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14974134#comment-14974134
]
Vyacheslav Lanovets commented on SVN-516:
-----------------------------------------
Hi,
Just in case somebody ever considers the feature, there are several use cases I
can dream up here:
1. svnadmin should be able to purge everything related to entities that were
deleted and not used since x time ago (before some revision).
2. end users can mark some already deleted entity for purging. But svnadmin
must be used to actually purge the marked data and all amend all related
revisions.
3. end users can mark for merging a range of revisions for some entity (like
rollback addition of 1GB of data to existing file).
Regarding why this is needed in our case. We had sourcesafe repository updated
to SVN (which tried to guess some revisions). Some commits date back to 199x.
As the original repo contained several projects, the resulting repo was copied
to several repositories; unrelated folders were deleted with plans for
individual security via Active Directory. Over time root directories in the
repositories were reorganized to reflect growing product needs. Later on, the
security was deemed not useful compared to *lost history* when transferring
files between repositories. And several repositories were combined back to one.
And after that the resulting directory structure was reorganized once more to
accommodate multiple projects, libraries, tools, sdks. As a consequence of so
many moves and reorganizations and copying, is that repository which maybe had
100000 interesting commits now has 250K revisions. As we quickly stopped
committing big binaries, it just less than 30G.
> svn obliterate
> --------------
>
> Key: SVN-516
> URL: https://issues.apache.org/jira/browse/SVN-516
> Project: Subversion
> Issue Type: New Feature
> Components: src
> Affects Versions: all
> Reporter: Ben Collins-Sussman
> Priority: Critical
> Fix For: unscheduled
>
>
> {noformat:nopanel=true}
> Some people want the ability to permanently remove a file, dir, or revision
> from
> history forever. This means rewriting the whole filesystem; a big deal. It
> would also break existing working copies.
> But hey, some folks want security. :-)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
