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

RE: Best practice, working copy and repository

From: Marziou, Gael <gael.marziou_at_hp.com>
Date: 2007-10-01 17:04:11 CEST

Maybe you should first start read about Subversion .
Do you know this free book?

http://svnbook.red-bean.com/

________________________________
From: Turner, Alexis (GPG) [mailto:Alexis.Turner@greenwood.com]
Sent: Monday, October 01, 2007 4:41 PM
To: users@subversion.tigris.org
Subject: Best practice, working copy and repository

Please forgive the newbie question - I've just inherited a website that uses Subversion which I have never used before.

The site I have is located in C:/Repository, and the working copy is checked out to D:/dev-server.

My confusion comes because the repository and working copy are mirror images of each other, all the way down to every branch and tag (of which there are a LOT). But based on the reading I did, I thought it was more standard to have the repository reflect all the branches, tags, snapshots, etc, and have the working copy only containing, say, the active branch.

I am a bit afraid to even check out a branch, because I am not sure the best procedure for checking out a branch in the working copy - do I merge it into the trunk in the working copy, and then also merge it into the trunk in the repository? What do I copy where?

I came up with this:
Copy C:/trunk -> C:/branch
Checkout C:/branch -> D:/samebranch
Commit (which sends everything back to the proper branch on C:)
Merge C:/branch -> C:/trunk

But I can't figure out how I get the completed D:/branch to D:/trunk. And I can't figure out how to make sure that my working copy is the correct single branch on D: and not the whole site or trunk.

Thanks for any insight.
-Alexis
Received on Mon Oct 1 17:05:10 2007

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.