Re: steps for synchronizing with production server

webpost_at_tigris.org wrote:
> What are the best steps for updating a local SVN with changes from production? We've got 20GB of files and on a last attempt, ended up with old repo (.svn) folders and a mess.
>
> Is there a more efficient way to migrate changes to the dev repository? Thanks for any advise.
>
> 1.) Copy PROD to LOCALPROD
> 2.) Remove LOCALPROD svn entries
> $ find -name .svn -print | xargs rm -rf {}
> 3.) Remove LOCALPROD orphans
> .... ?
> 4.) Copy LOCALPROD over LOCALDEV
> $ cp -rf * LOCALDEV/*
> 5.) Update subversion repo
> $ su sync_user && svn update && svn commit -m'updating from production'

Subversion isn't designed to have multiple copies of the repository.
Why don't you just copy to a branch in the production repository for
whatever non-trunk development you are doing so you'll be able to merge
subsequent updates?

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2330775
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].