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

Re: [TSVN] RE: Feature Suggestion: Ability to specify dedicate path for .SVN folders.

From: Simon Large <simon_at_skirridsystems.co.uk>
Date: 2005-09-19 11:01:24 CEST

Paul Coddington wrote:
> However, I can see that you could go either way, and certainly having
> "trunk" and "branches" in your working copy (as you suggest) saves
> switching and makes check outs a single click process, and having the
> working copy tree and repository tree identical would be conceptually
> simpler for the 'newbies' on the team.

That depends on how you want to use branches. Often they are used to
isolate changes made by one person/team, so you don't necessarily want
everyone else to be picking those up as well: a) because it wastes
bandwidth for them on an update, and b) because it hides the development
clutter from those who don't need to see it yet. But you are completely
free to disagree - there is no harm in doing it that way.

> The idea here was that for those who want to use 'switch', it would
> be handy if you could just checkout the root of the repository and
> only have 'trunk' come out for all projects as if the 'trunk' folder
> were absent from the working copy paths. If no-one has asked for
> this before, I would guess most people are using the 'one project per
> repository' approach or the 'have root and branch folders checked out
> and do not use switch' approach.

Again, the way you organise your repo is entirely up to you. You could
dispense with /trunk altogether and put stuff in the root, maybe with
branches as a subfolder. Of course, even if you have trunk, that doesn't
mean you have to have a folder of that name in you checkout.


Checkout trunk to C:\MyWC


It is often helpful to have a tags folder to record snapshots of the
project, typically at version release time, and it is better to keep
those outside the normal checkout, simply because once you have made a
lot of snapshots, the size of a standard checkout will grow to monster
proportions if all the tags are included.

So you could have a structure like:


You can checkout dev/ and get both trunk and branches, or you can just
checkout trunk and use switching to pick up a branch. Or you can have 2
separate checkouts for trunk/ and MyDevBranch/. Or you can throw away
trunk/ and put the content directly in dev/ with branches as a
subfolder. Nothing is compulsory, it's just a file system.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Sep 19 11:02:36 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.