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

Re: Chained svns

From: John Doe <jdmls_at_yahoo.com>
Date: Thu, 25 Sep 2008 08:57:36 -0700 (PDT)

> > Does snvsync handle updates as patches too?
> Yes.
> > Like, if I change 1 line in 500 1000000 lines files, will it
> > transfer 500 one line diffs or the whole 500 files?
> It will transfer just the diff.
> As it was explained to me by Ben Collins-Sussman, svnsync effectively
> checks out each revision from the source repository and commits it to
> the destination repository.

One last question about the migration:
So, right now we have the repo at the datacenter and we ci from the office.
Would something like the following be safe to migrate to these dev/prod chained repos?

  dump prod.repo at the datacenter
  load prod.repo at the office
  sync the office repo to the datacenter repo

Since, right after the migration, both repos will be identical (right?), can I just leave it that way or should I delete the old repo at the datacenter and then sync it back from the office?
Do I need to remove the .svn dirs from the office and/or prod to regenerate them?
Do you foresee any tricky situations?



To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-25 17:58:02 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.