Re: svn switch to an incorrect branch deletes modified local files

On Wed, Apr 23, 2008 at 5:06 PM, Karl Fogel <kfogel_at_red-bean.com> wrote:
> "David Glasser" <glasser_at_davidglasser.net> writes:
> >> No, switching to a new working copy rooted in the current directory is
> >> fine -- people do it all the time, and Subversion has no way to know
> >> whether it's right or wrong for your given situation.
> >
> > Eh, I deny that it's "fine"... the current working copy code has a
> > high probability of breaking your wc if you do a weird switch (issue
> > #2505). This broader issue probably is easier to fix in a wc rewrite
> > which constructs a full metadata tree before actually trying to muck
> > with user files.
>
> It may be buggy, but it is an intended feature. I do such switches all
> the time. In fact they are the majority of switches I perform (because
> I'm switching from one branch to another, or trunk to/from a branch).

Er, I guess my real position is: "svn switch should be able to do
arbitrary switches, but in practice it just doesn't work unless you're
switching between multiple branches at the same level (including trunk
of course); and when it doesn't work, it's usually unrecoverable".

Though the bad cases I'm referring to are exactly the opposite of what
you just said... "switching from one branch to another, or trunk
to/from a branch" are the svn switch cases that I expect to not break.

--dave

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org