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

[TSVN] Working Copy

From: Peter McNab <mcnab_p_at_melbpc.org.au>
Date: 2005-01-17 11:28:37 CET

I'm unsure whether these are questions for this list or the SVN list.

However seeing it relates to comments that are issued by TortoiseSVN I'm
assuming the question can best be put to this list.
After getting TortoiseSVN to create a branch I get the popup note going
on about using the Switch command in relation to "the working copy".
Now I consider I have a more than one working copy (WC) for a single
project that is currently under version control, being:-
1. The head of the trunk, (with on going minor but important updates)
2. The head of each unmerged branch, (with ongoing significant
project development)
Besides the trunk, which is always working, the branches too are usually
fully functional and in my view "working".
So in what context is TortoiseSVN meaning when it says "working copy"?
Does it mean functional or does it mean being worked upon.

If I use TortoiseSVN to "switch" working copies say from trunk to a new
branch, as suggested, what exactly happens to the files on my local
machine and are there any followup commands necessary to complete the
operation such as "Update" or "Commit"?
If so why not have these incorporated automatically by TortoiseSVN?

If there is more than one active branch, on a local machine does one
have to "Switch" from one branch to the other and back again to make and
commit changes?

Having "Switched" a working copy, is there some state or property that
can be examined to see which is the current working copy?

I have read the SVN docs too and they still haven't quite made sense,
there being no appraent equivalent in CVS that I can relate to.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Jan 17 11:29:30 2005

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