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

Re: switching with externals issue

From: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Tue, 1 Jul 2008 13:24:19 +0100

2008/7/1 Pieter Bezuidenhout <pieter_at_jhb.acuo.co.za>:
> Case 1)
>
> The working folder is currently on the trunc which has the following
> external
>
> ^/lib ext/lib
>
> Switching to another, let's say emty, branch will causes the versioned lib
> folder to be deleted but will leave the un-versioned ext folder. This works
> as expected.
>
> Case 2)
>
> The working folder is currently on the trunc. Underneath the trunc is a
> versioned folder named ext.
>
> The ext folder has the following external
>
> ^/lib lib
>
> Switching to another, let's say emty, branch, from trunc, will not only
> cause the versioned ext to remain but also the versioned lib folder. It is
> expected that the lib folder should at least be deleted as is the case in 1.
> Also, any versioned and up to date, relative to trunc, folder should be
> deleted which is wat normally happen when you switch.
>
> Case 3)
>
> Case 1 but with ext being versioned before the external is applied. Behaves
> simalarly to case 2.
>
>
> Is this a bug or is there a rule stating that there should be no versioned
> folders between the folder being switched from and the external folder?

This is handled by the subversion library. You need to report this on
the subversion users mailing list (users <at> subversion.tigris.org).

Simon

-- 
: ___
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-07-01 14:24:32 CEST

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

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