"Jon Skeet" <Jon.Skeet@clearswift.com> wrote on 03/01/2006 10:08:49 AM:
> It seems to me that Team->Copy has at least two bugs in it, as well as
missing
> functionality.
>
> I came across Team->Copy when investigating the broken behaviour of
normal
> copy/paste of a folder. Here's what I've found:
>
> 1) If you Team->Copy a folder to elsewhere within the same project, it
tries
> to do an svn copy. However, it tries to copy it *to* a working copy
based on
> the workspace directory + project name.
>
> 2) If you Team->Copy a folder to a different project, it tries to do an
svn
> export even if the other project is under source control as part of the
same
> repository. Again, the destination appears to be formed assuming that
the
> project lives in a subdirectory of the workspace.
>
> 3) There's no way I can see to copy the folder and change its name, as
you can
> with the normal copy/paste operation (if it already exists).
>
> The assumption about the destination is particularly worrying - we name
our
> projects differently to the directories containing them (for reasons of
> disambiguation) and we keep our source separately from our workspace.
>
> I couldn't immediately see any open issues about this, but perhaps I've
missedsomething?
There are no open issues about this, so you'll have to create them.
On #2 we were being conservative as the svn copy command is not very
robust on copying between isolated WC's.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 1 16:26:39 2006