Ben, thanks again for your clarification. Very helpful!
Victor. PS. and thanks for the svn book! On Tue, May 12, 2009 at 10:58 AM, Ben Collins-Sussman <[email protected]>wrote: > > On Tue, May 12, 2009 at 9:41 AM, V!ctor Adán <[email protected]> wrote: > > > > This suggests that svnsync is just doing a playback / record of all the > > commits. But then the warnings that follow and the constant reference to > > mirror repositories made me wonder if there was not some kind of > dependency > > being created in the target repository. > > There is a dependency created in the target repository. If you look > at the revision props on r0, you'll see some info that shows that the > target repository remembers the source repository's URL, and how far > it got in the last sync. This allows you to run 'svnsync' as a cron > job to routinely mirror the latest commits from source to target. If > the revision numbers ever get out of step, however, svnsync mirroring > will break. In other words, if svnsync thinks it needs to replicate > revisions 52, 53, and 54 from source to target, and then discovers > that the target's HEAD is *anything* other than r51, it will error out > and fail. > > In your case, though, it just doesn't matter. Mirror everything once, > then toss away the source repository forever. The target repository > becomes your new home to continue work in. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at Google Code" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en -~----------~----~----~----~------~----~------~--~---
