I don't get the feeling that this leaves traces keeping the repository arguably auditable. One of the key blockers of getting this functionality in Subversion is that while there is value in removing things from the repository, it shouldn't be done in a manner that leaves no trace. One cannot assume that such functionality is only used for the appropriate use cases and claiming a repository is auditable while being able to remove files/revisions in a manner that leaves no breadcrumbs is inaccurate. If traces are left (e.g., filenames with information on who removed the content, when and for what reason), then obliterate is useful and retains the core requirement that history, all history, is retained or at least accounted for.
Regards, Bob Jenkins On Thu, Feb 4, 2016 at 6:17 AM, Doros Agathangelou (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/SVN-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15132161#comment-15132161 > ] > > Doros Agathangelou commented on SVN-516: > ---------------------------------------- > > I would like to draw the attention of the community to a tool we developed > that solves the problem of obliterating files from svn repositories. The > tool is called [Subdivision|http://subdi.vision] and while being a > commercial offering, it is free for small repositories and open source > projects. > > Subdivision starts off by analyzing the repository to identify the moves > and copies of the repository's files and folder. As the user makes the > selection of which files to obliterate, Subdivision will select aditional > files that have to be obliterated (or preserved) depending on the move and > copy history. This removes all the problems that might occur when using > svndumpfilter such as the "Invalid copy source path" error. > > In addition to the obliterate functionality, Subdivision can split a > repository in two parts while guaranteeing that all files will make it in > at least one of the resulting repositories, as well as extract files files > into a new repository. > > > > > > 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) >
