Stefan Sperling wrote on Tue, Nov 22, 2011 at 15:04:01 +0100: > 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).
Perhaps operate at revision granularity? That is, devise a way to encode an editor drive in a file[1], and have svnsync/svndumptool drive a specific revision from that file rather than from their usual data source? svnsync sync --exception r42=/tmp/new-r42.svndrive $URL $URL2 [1] implemenetation detail: would probably be more convenient to store the new-file-contents in separate files than inline in one massive file.
