[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 18:35:48 +0100

-----Original Message-----
> From: Kurt Pruenner [mailto:leak_at_gmx.at]
> Sent: Monday, June 01, 2009 2:41 PM
> To: users_at_tortoisesvn.tigris.org
> Subject: Re: How to manage one project but wtih two repositories
> Bolstridge, Andrew wrote:
> > 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).
> Doing a relocate from one repository to a totally different one? I
> doubt
> that's gonna work.

I didn't think it was a totally different repo, it's the same one without some changes that need committing. I'm not sure if this is the best way, but it should work.

> > 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.
> This is about CodePlex[1], Microsoft's SourceForge clone. They use Team
> Foundation Server for version management with some kind of SVN bridge
> for checking out code using SVN, but that's of course read-only.
Codeplex may be a TFS backend with a SVN fa├žade, but it is still read/write. You can happily commit changes using SVN. I've done it.


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