# Re: [TSVN] Re: Working Copy

From: SteveKing <stefankueng_at_gmail.com>
Date: 2005-01-17 15:38:12 CET

On Tue, 18 Jan 2005 00:34:06 +1100, Peter McNab <mcnab_p@melbpc.org.au> wrote:

> What I still don't fully understand is the concept of WC.
>
> On my "server" there is a repository containing a trunk which provides
> the latest stable release and in the same repository a branches folder
> containing one or more purpose named branches.

Don't confuse /trunk with release. /trunk is usually used as the place
where the development takes place. To mark a release, make a copy into
the /tags/ folder.

> On the local machine (LM) I have the same folder structure.

You mean you've checked out from the repository root? Not from e.g. /trunk?

> The LM trunk folder is populated with the files that represent the head
> of the trunk.
> The LM branches\specialbranch folder is populated with files that
> represents the tip of that branch.
> Both can represent working (correctly executable) copies of code (files)
> but I suspect that that's not what TSVN means by WC.

"Working copy" doesn't mean "working" in the sense that it is somehow
stable or can be compiled without errors. "working" means here that
you have a copy of all the sources on which you can work on, i.e.
modify them.
That's to the repository, where your files are stored, but you can't
work on them directly (you have to make a copy of those files on your
local harddrive). And that local copy of the sourcecode/files is calle
*working* copy.

> So is the purpose of the "switch" command and the TSVN expressed notion
> of singular WC a means to allow users to have just one set of files at a
> time on the LM and "Switch" to another set of files in the same folder
> location, with the minimal network traffic to effect a full file change
> from say branch1 to trunk to branch2 etc?

The switch command is usefull if you have a large working copy. In
such cases, most people don't want a copy of /trunk and each branch,
they just want one local copy of e.g. /trunk. Then, when they have to
do some work on a branch, they don't have to check out a whole new
copy (working copy) of the branch, but can *switch* their working copy
of /trunk over to the branch. Subversion then 'converts' that working
copy so that it looks exactly as if it were checked out from that
branch.

Stefan

```--
___
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