Yes, to co trunk...
svn co svn://reposMachine/My_Project/trunk
To co branch...
svn co svn://reposMachine/My_Project/branch/branchName
To co a certain release
svn co svn://reposMachine/My_Project/tags/tagName
Yes this checks out ALL of the repos
svn co svn://reposMachine/My_Project
You can define environment variables for shortcuts...
setenv PROJROOT svn://reposMachine/My_Project
setenv PROJTR $PROJROOT/trunk
setenv PROJBR $PROJROOT/branches
setenv PROJTG $PROJROOT/tags
But that does NOT eliminate the fact that you still
need trunk, branches and tags to co the corresponding
files.
-chris
>-----Original Message-----
>From: Andrew Close [mailto:aclose@gmail.com]
>Sent: Wednesday, February 14, 2007 10:56 AM
>To: users@subversion.tigris.org
>Subject: n00b: branches, tags, trunk...
>
>please correct me if i'm wrong, but 'Best Practices' seem to
>indicate that at the top level of your repository you should
>have directories labeled 'branches', 'tags', 'trunk', that
>contain your branches, tags and trunk. :)
>
>a question i have regarding this setup is when i specify my
>repository URL for a checkout, do i always have to list either
>'branches', 'tags', or 'trunk' as part of the URL?
>for example, my repository is called 'My_Project'. in the
>root of my project i have the three recommended directories.
>and since this is a new repository i've only populated the
>'trunk' with my project files.
>so now a developer wants to perform a checkout to populate
>their local workspace. for the URL to the repository they would enter:
>'svn://reposMachine/My_Project/trunk'. if the developer
>wanted to check out a specific branch, assuming there were
>branches to check out from, they would enter:
>'svn://reposMachine/My_Project/branch/branchName' as their URL.
>is this correct? or is there a way around having to enter
>'branch', 'tags', 'trunk' in the URL?
>when i've tried just entering: 'svn://reposMachine/My_Project'
>as the URL i end up getting all branches, tags and the trunk
>in my local workspace.
>
>thanks for any comments, corrections, etc. :)
>
>oh, are there any docs that list out 'Best Practices' aside
>from the SVN Book? i've been trying to read through the docs
>listed on the site just to get up to speed.
>
>thanks again
>andy
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 14 17:18:46 2007