subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Shahaf <...@daniel.shahaf.name>
Subject Re: Repairing or removing broken revisions
Date Tue, 14 Aug 2012 22:10:58 GMT
PR wrote on Mon, Aug 13, 2012 at 22:12:51 -0700:
> On Mon, Aug 13, 2012 at 7:10 PM, Trent Fisher <trent.fisher@oracle.com> wrote:
> > svnadmin dump -r0:44444 /some/repos > p1
> > svnadmin dump --incremental -r44445 /some/repos > p2
> > svnadmin dump --incremental -r44446:HEAD /some/repos > p3
> > Then I manually doctored p2 to indicate that the rev is broken (but leave
> > the original comment intact), then load all three into a fresh repository
> > (cat p1 p2 p3 | svnadmin load /some/new/repos)
> >
> > The advantage of this is that the uuid and rev numbers remain the same, so
> > existing workspaces will work.  And this would preserve all other history of
> > the given file.
> >
> > I just did this on a production repository two weeks ago, and no complaints
> > so far.
> >
> > trent...
> >
> 
> 
> >>> I would do slightly differently ..
> >>> let us say that 5 10 and 15 are 3 revs of the file to keep it simple
> >>> as suggested before I would do the three part dump
> >>> but I will load to 9 then look at the diff beween 9 and 15 subtract the
diff for 15
> >>> and checkin as rev 10 to the repository with the expected log and not failing
to mention
> >>> that this was engineered checkin [ it will be difficult if the files # are
more for a checkin ..in my case was max
> >>> 2 some times 1 file .. since we migrated from CVS
> >>>... then continue on to load 11 to 15 ..
> >>> just my 2c ...
> 
> sorry if I accidentally broke the posting sequence...

You didn't break threading, but you preceded yoru text by three
">"-quoting levels instead of the normal zero.

Mime
View raw message