[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: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Mon, 1 Jun 2009 14:11:28 +0100

> -----Original Message-----
> From: Mark Breen [mailto:marklbreen_at_gmail.com]
> Sent: Monday, June 01, 2009 12:38 PM
> To: users_at_tortoisesvn.tigris.org
> Subject: How to manage one project but wtih two repositories
> In other words, we commit on a daily basis to our private server used
> by 10 - 20 people, but once or twice a month, we can to make a
> of that code and {Commit / publish / replace} the code on the public
> site.

Surely you just checkout the full set of source from your private
repository, then use the 'relocate' command to change the url to the
public repo, and then commit (you may need to update first to refresh
the base entries).

Alternatively, if you already have a public WC, why not just merge your
changes since you last performed a released into it.

Third option - checkout the latest public repo, export your private repo
to a new directory and then copy those files on top of the public WC and
commit it. I'd do this.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-01 15:12:31 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.