On Tuesday, November 22, 2011 3:04 PM, "Stefan Sperling" <s...@elego.de> wrote: > On Tue, Nov 22, 2011 at 01:32:02PM +0100, Johan Corveleyn wrote: > > > > Having a way to do this with svnsync and svndumptool would already be > > very useful. It would at least give some assurance to svn admins that > > these things are 'repairable'. Being able to fix a live repository > > would of course be even better :-). > > Editing dump files has always been the approach to fixing up mistakes in > history. So I don't think we need a change in the FS backends. Instead > we need better dump file editing capabilities. svndumptool might go > part of the way. But ideally this would be built into svndumpfilter or > a new offical tool that edits dump files (rather than just filtering > nodes from a dumpfile).
I may have hinted at that in my previous mail, but one thing I think is possible is a tool that edits $REPOS/db/ offline. That is, if there are changes which are easy to effect to a filesystem tree without re-creating all the "remainder of history", then a tool that effects them --- without catering for concurrent readers, or even for before-it-started-its-thing readers --- might be writeable and useful.
