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

Re: Noob Question

From: Ryan Schmidt <subversion-2008b_at_ryandesign.com>
Date: Sun, 1 Jun 2008 18:04:03 -0500

On May 31, 2008, at 02:16, Kurt Federspiel wrote:

> I have a repository that stores source code written for a WinXP/
> 2003 application. We are in the process of porting to Linux, and
> want to set up a new repository to hold the ported code. The
> project and directory names are the same.
>
> So I have:
> /Repositories
> /Repositories/Win
> /Repositories/Win/xmlrpc
> /Repositories/Linux
> /Repositories/Win/xmlrpc
>
> /Repositories/Win and /Repositories/Linux were created with
> svnadmin. Whenever I try to svn add/update/commit to the /
> Repositories/Linux/xmlrpc, I get a revision around 226, which is
> (obviously) the Win Repository (since the Linux Repo is brand new)
>
> Am I being stupid? I want to keep the sources separate for now, so
> how do I add/update/commit to the /Linux Repository? Can someone
> please help me be unstupid??
>
> Thanks.
> Kurt The Noob.
>
> PS. For setting up an apache server, having one repository, and
> getting several clients running, SVN was the bomb; it took me about
> 80 minutes to do it. If only EVERTHING were this easy...hats off
> to the dev and support teams.

I strongly recommend you keep both versions of your product in a
single repository, since you cannot merge or copy between
repositories, only within a repository. Separate repositories should
only be used for projects or concepts which are totally separate from
one another. For example, I have one repository for source code, and
a second repository for music.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-02 01:04:35 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.