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

Re: svn switch question

From: Jeremy Pereira <jeremyp_at_jeremyp.net>
Date: 2007-11-02 19:28:40 CET

On 2 Nov 2007, at 14:28, Steven Bakke wrote:

>> Perhaps, but I still can't wrap my head around why he needs to do
>> this.
>> I can't answer his question, either, because I don't think what he
>> wants
>> is possible. I suspect my problem with this is due to the number of
>> years I've been working on Java or DotNet style projects.
>> Generally, I
>> don't see any value in arbitrarilly switching subprojects around.
>> Maybe
>> in a more low-level environment, like C, where such rigid
>> project/package definitions don't exist, this kind of mixed bag is
>> more
>> logical.
>> Unfortunately, I have to step back from this problem because I cannot
>> offer any constructive ideas. I do want to understand the reason for
>> this scenario, though.
> I was thinking that I'd like to boil this problem down a bit further.
> Let's say I want to take a look at what is in another tag for one
> of my subdirectories:
> % cd <work>
> % svn switch <tag-URL> <work>/A

Why would you want to do that though? Surely, you'd just check out a
working copy of the tag into a different directory, not in your
source tree.

My feeling is that if you have a source tree where you might
legitimately want to pull in sub directories from different tags,
then the sub directories are actually independent components and
should be treated as such and referenced using svn:externals.

> (Look at the files and do whatever. No modifications)
> Now lets say I want to switch back to trunk, since I'm done looking
> at whatever was in that tag.
> % svn switch <trunk-URL> <work>/A
> When 'A' had been deleted from trunk in the interim, there is no
> way to do this. In my opinion, this is a flaw in subversion.
> Regardless of whether you understand the reasoning for it, I
> believe you should always be able to "undo" a switch successfully.
> I'm thinking this is somewhat related to the "depth" issue being
> dealt with in 1.5. Once a directory becomes part of the current
> working copy, it is impossible to remove it.
> Lastly, the common "solution" suggested for cases such as this is
> to do a fresh checkout. That's not really a good option in a
> number of cases. I should be able to issue a legal series of
> commands to get me back where I was considering that I didn't do
> any local modifications.
>> --
>> David
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 2 19:29:49 2007

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

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