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

Re: How to manage one project but wtih two repositories

From: RobinP <robin.pellatt_at_gmail.com>
Date: Wed, 3 Jun 2009 03:00:18 -0700 (PDT)

I can't believe nobody has suggested this yet, but if I have
understood correctly your public repo is read only, so it sounds to me
like svnsync is exactly what you need: http://svnbook.red-bean.com/en/1.4/svn.ref.svnsync.html

On Jun 2, 8:14 pm, Alexander Iljin <ajs..._at_yandex.ru> wrote:
> Hello!
> MB> 1) check out all code from private server
> MB> 2) check out all code from public server
> MB> 3) delete all code from public WC
> MB> 4) copy all code from private WC to public WC
> MB> 5) commit all code from newly updated public WC
>   I'm thinking of a way similar to vendor branch. Say, "Priv" is your
>   private repo, "Pub" is the public one.
>   - tag the last revision you've uploaded to public:
>     Priv/tags/pub1
>   - for a new release make another tag:
>     Priv/tags/pub2
>   - checkout the Pub/trunk to Pub.wc
>   - diff Priv/tags/pub1 vs. Priv/tags/pub2, make a patch
>   - apply the patch to Pub.wc
>   - commit Pub.wc
>   I'm not an expert in the diff/patch stuff, so I don't know if
>   copy/rename/move operations will be handled properly (someone,
>   please, comment on that). If so, you can automate the thing with a
>   command-line SVN client.
> ---=====---
>  Alexander
> ------------------------------------------------------http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMess...
> To unsubscribe from this discussion, e-mail: [users-unsubscr..._at_tortoisesvn.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-03 12:05:56 CEST

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

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