[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: differences in dump/load/dump cycle

From: Nico Kadel-Garcia <nkadel_at_gmail.com>
Date: Fri, 5 Aug 2016 21:26:23 -0400

On Fri, Aug 5, 2016 at 10:06 AM, Vincent Lefevre <vincent-svn_at_vinc17.net> wrote:
> On 2016-08-03 16:10:16 +0200, Stefan Hett wrote:
>> On 8/3/2016 3:40 PM, Nico Kadel-Garcia wrote:
>> > [export/import instead of dump/load]
> [...]
>> In your export/import approach you would do:
>> export -> import -> export -> compare old vs. new export
>> And like with the dump/load/dump approach above, if you see a difference
>> between the two exports you would then investigate their cause.
> export -> import -> export is less safe: how do you know that what
> has been exported is "correct"? Note that with old repositories (and
> perhaps this is still possible with some external tools), starting
> with revision R1 and successively upgrading to R2 may give a different
> result from just getting R2 without intermediate revisions. If the
> problem is unnoticed, information may definitively be lost in the
> repository started from the export.

This seems to work pretty well

      diff -r --exclude=.svn \
[directory of old repo checkout] [directory of new repo checkout]

Parsing through the old logs for identical logs is one of the most
time-wasting abuses of manpower I've ever seen in a migration. They
keep being *wrong* from the accumulated history of old bugs.

Leave the old repository around for history if you want, but every few
years, shake the cobwebs off your project and start over from a clean

> Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Received on 2016-08-06 03:26:32 CEST

This is an archived mail posted to the Subversion Users mailing list.