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

Re: Beginner question on trunks, branches and tags

From: Jody Shumaker <jody.shumaker_at_gmail.com>
Date: 2006-03-19 18:50:12 CET

On 3/19/06, Milen A. Radev <milen@radev.net> wrote:
>
> I presume you've read the appropriate chapters in the SVN Book -
> http://svnbook.red-bean.com/nightly/en/svn.reposadmin.projects.html#svn.reposadmin.projects.chooselayout?
>
> OK, most of that applies to fairly big projects. In your case you
> could just forget about those directories. But if you are not sure how
> your simple (now) web project could wind up, create "tags", "branches"
> and "trunk" in the repository, import all files and subdirs from your
> web project dir in the "trunk", rename the project dir, create a new
> dir with the old name, checkout the "trunk" in it and continue your
> work.
>

I'd still highly recommend you atleast create the /trunk/ base
directory and place everything in there. The main reason for doing so
is that later on if you do decide you want to create a tag/branch of
everything, you have a single base object to do it from. Creating the
branches/tags directories can always be done later if you decide to
use them, but creating the trunk/ structure later is annoying as you
have to create the directory, then move everything into it, and then
everyone checking out from the project has to switch urls.

By just creating the directory it doesn't hurt you beyond having to
type 6 more characters when doing a checkout, and can really save time
later on when you do understand branching and decide you might want to
use it.

- Jody

- Jody

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Sun Mar 19 18:50:23 2006

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.