Re: svn switch problem - cannot switch from ''unclean'' checkout

2007/7/11, james coleman <jamesc@dspsrv.com>:
> We had a bit of a problem with using svn switch.
> If doing a switch and there are unversioned (maybe ignored) items in the checkout
> then you can get errors and end up with an unusable repository.
> We now keep a ''pristine'' clean checkout of any trunk or branch that is worked off of
> and update it then copy and switch when we need to checkout.
[SNIP]
> I think the switch problem is a puzzling one as to me it seems natural that if
> an svn status reported that there were no changes to versioned files then a
> svn switch would do the right thing and warn and move unversioned files out
> of the way. The need to do switch only from pristine checkout is also not
> mentioned in svn manual.

I experimented this several times too (both with subclipse and TSVN).
Usually I "fix" it by doing some manual clean-up and executing update
and revert alternatively until my WC is OK. Never understood what's
was happening. Thought I did something wrong (not the case
apparently).

This is very annoying, since switch is very useful when working with
lots of branches and the WC is big. (I used to maintain separate co of
each branch when I worked with CVS and hoped to get rid of them now
with svn.)

-- 
Ir. Arnauld Van Muysewinkel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org