> -----Original Message-----
> From: Stefan Sperling [mailto:[email protected]]
> Sent: dinsdag 8 januari 2013 14:58
> To: Mark Phippard
> Cc: Johan Corveleyn; Philip Martin; Bert Huijben; Daniel Shahaf;
> [email protected]
> Subject: Re: 'svn mv' between disjoint wc's of disjoint subtrees
> Also, it seems that Eclipse could gain an advantage anyway by switching to
> a model that encourages a single sparse working copy for all projects that
> share the same repository. The user won't notice a difference, and many
> operations will be faster (e.g. update/switch with serf won't have to
> get the same files twice).
If you don't have read access on the root of the repository, or are not
flexible in your working copy layout (E.g. your make files depend on a
layout), this is not an option.
Both cases are very common.
In Visual Studio, there are still many users that have their websites
somewhere on C:\inetpub\..., with all their projects somewhere else (e.g.
F:\projects\....). They certainly want to manage those with one Subversion
client.
Bert
