Eiren Smith wrote on Wed, 16 Jun 2010 at 00:25 -0000:
> On Jun 15, 2010, at 5:02 PM, Ryan Schmidt wrote:
> > On Jun 15, 2010, at 15:37, Eiren Smith wrote:
> > > I considered doing it the way you described. Unfortunately, most of the
> > > seven (7) missing revisions are for binary files (DLLs and DOCs) and so
> > > I can't reproduce their variations by hand. And since SVN is storing
> > > binary deltas, not entire files, for each commit, I believe I would have
> > > to reproduce them perfectly to get this particular solution to work.
> > >
> > > Any ideas how to get around this or where to go from here?
> > Perhaps you can do all the "svnadmin dump" steps. Then use svndumptool to
svndumpfilter or svndumptool, either way it's better than patching (as
I suggested) :-)
> > filter the problematic files out of all the dumps after which a revision
> > of their history was lost. Then you can load these dumps in order into a
> > new repository.
> Perhaps. Unfortunately, for just one of the seven missing revisions (rev.
> 7519), I don't have a record of what files were changed. I think that will
> block me unless I can find a tool that will build a dependency tree/map for
> me from that revision through to the HEAD.
> Any ideas?
1. Proceed without this information --- you'll get it from svnadmin's
errors during the load :-)
2. Considering the format of rev files, it might not be that hard to look
in the remaining rev files for where they depend upon the missing ones.
I'm not sure if there is a tool for that, though.
Received on 2010-06-19 18:30:59 CEST