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

Question on svnsync

From: Karl Heinz Marbaise <khmarbaise_at_gmx.de>
Date: Wed, 03 Feb 2010 23:52:48 +0100


i have observed a strange behaviour of svnsync in partially replicating
  a repository (In my opinion)..

Created a local repository (svnadmin create...) change the
pre-revprop-change hook to accept changes...and then
i initialized svnsync like the following:

  svnsync init file:///usr/local/test/t

Now i started svnsync sync file e:///usr/local/test/t ....

And based on that it seemed to be that all revision properties from
1...to whatever revision the real information starts will be copied into
this repository...and in this case it would take a looooonnnnngggg time...

So that means that the replicated repository has all revision properties
(log messages etc.) of about 800000 revisions...and after that all
information is coming which interesting for me...

So my suggestion is to think about an option for svnsync sync -r
StartRev where to start with the synchronization or may be let svnsync
analyze itself where the first revision is in which the folder
/subversion exist ?

So what do you think?

I understand that if svnsync wouldn't replicate the revision properties
the revision numbers of the replicated repository will change ...but for
a partially replicated repository might that not be a problem ?

But what about just creating the revision properties in an other way (by
svnsync itself) without content wouldn't that be faster?

Kind Regards
Karl Heinz Marbaise

SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de
Received on 2010-02-03 23:53:25 CET

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