Hi Simon
Thanks for a well written reply. I sincerely appreciate the help I am
receiving for respondents.
I am still coming to grips with the terminology and paradigms, some of
which have probably evolved in the unix side of computing. When injected
into my windows centric world they seem to loose their true or full
meaning, (for me anyway).
Hence what might seem like very dumb questions, are really only
reflections of my confusion.
I have read and re-read the SVN documentation several times before
seeking clarification so it's not necessarily a TSVN doco issue.
Regards
Peter McNab.
Simon Large wrote:
>You should read the SVN book, which describes the difference between
>Update and Switch. Sorry, don't remember the chapter reference. Often
>there are only minor differences between two branches. When you create a
>branch, most of it is a cheap copy from somewhere else (often the
>trunk), so if your WC is currently reflecting the repository trunk and
>you want it to reflect a branch, it will not require many changes.
>
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.
On the local machine (LM) I have the same folder structure.
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.
I can and sometimes do work on both sets of files simultaneously with
different update intentions so in my mind I have two WCs but the TSVN
warning conveys the notion that "Working Copy" is a singular thing. So,
if I had umpteen special branches
and the project was very large there would be a considerable duplication
of code on the ML.
>And that is exactly where Switch helps you.You could do a fresh Checkout from the branch, but it saves a great deal of bandwidth to use Switch to
>modify your WC so that it is based on the branch instead of the trunk.
>All it has to do is update the files which are different. It will also
>delete (version controlled) files in your WC which were in the old
>branch but not the new, and it will add files which are in the new
>branch but not the old. Unversioned files wil not be touched of course.
>
>
>
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?
Regards
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 17 14:34:45 2005