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

[TSVN] Re: Working Copy

From: Jens Scheidtmann <Jens.Scheidtmann_at_bayerbbs.com>
Date: 2005-01-18 11:58:33 CET

news <news@sea.gmane.org> writes:

> Peter McNab wrote:
[...]
> > 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.
>
> There is nothing wrong with having multiple WCs, but as you say it takes
> up a huge amount of space for code which is mostly duplicated. The "SVN
> way" to handle this more efficiently is to have a single WC and use the
> "Switch" command to convert it from trunk to branch, or BranchA to
> BranchB.

To avoid lengthy downloads (over slow links) you can even copy your WC
to a different location (local on disk) and then switch, which is
equivalent to check out two WCs, one from e.g. trunk and the other one
from the branch you switched to.

I will try to give a definition:

A Working Copy (abbr. WC) is a copy of a directory of a repository
which is stored on your local machine. That means the top most
directory containing a .svn subdirectory and all it's children. It is
the result of a checkout operation. In addition it may contain your
local changes and additions (files and directories). It's the thing
you're working on.

Jens

-- 
Jens.Scheidtmann@bayerbbs.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Jan 18 15:42:53 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.