Re: [TSVN] 1.2.2... sad story
From: Flex <flex_at_datecs.bg>
Date: 2005-09-07 17:06:11 CEST
Wednesday, September 7, 2005, 3:34:14 PM, you wrote:
> On 9/7/05, Flex <firstname.lastname@example.org> wrote:
>> the 4347 build solved the problem with moving .svn folders, but still the
> The problem of sub-duplicates is a Subversion issue I complained about
But this is serious... considering that a single move of an "external" folder sets its status "Deleted" and it is actually executed the next commit thus ruining the external folder and all other projects that depends on it can't be checked out anymore. This is especially true for a "shared" folders since all other tends to used them - after the move now I can't checkout any of my projects anymore.
I can't get the big picture here since I'm pure tsvn user but... here's what I think happens: Just a simple misunderstanding between what user wants to do and how tsvn executes it:
this external dir cames as "svn:externals externaldir //external/repository/externaldir" property set on the trunk folder.
So the user(me) selects all folders inside project/trunk and tsvn moves them to another folder. In the case of dir1 and dir2 it is ok, however "externaldir" gets "moved" to the new folder with svn mv, hence deleted from the original location, while in this case it should be just shell-moved, skipped or operation aborted, anything but without executing a svn mv command on it.
However... can tsvn "mark" such a directories and use a shell move or just fail or skip instead of svn mv on them?
This is an archived mail posted to the TortoiseSVN Dev mailing list.