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

james coleman <jamesc@dspsrv.com> writes:
> Here is the text of the FAQ entry I think would work:

Thanks, I think this is worth having in the FAQ. Can you send it to
dev@ as a patch, using the instructions at

   http://subversion.tigris.org/mailing-list-guidelines.html#patches

See comments below...

> Why doesn't svn switch work in some cases?
>
> In some cases where there are unversioned (and maybe ignored) items
> in the working copy then you can get errors and end up with an
> unusable working copy. The more complex the changes on branch and trunk
> the more likely this is. See issue 2505.

If you could provide some examples of local changes that are *not*
likely to interfere with switch, that would help; adding other
examples of changes that are likely to interfere would be great too.

Remember, the reader will be asking themselves "Am I in trouble or
not?" Anything we can do to help them know the answer to that
question is good.

> A switch from a pristine clean checkout always works. There are two
> ways of working if you are using svn switch as part of your development
> process:
>
> 1. Fully clean your working copy of unversioned (including ignored)
> files before switch.
> WARNING! This deletes all unversioned dirs/files.
> Be VERY sure that you do not need anything that will be removed.
>
> alias svn-unversioned='svn status --no-ignore | grep "^[I?]" | sed 's/^[I?]//''
> alias svn-clean-wc='svn-unversioned |xargs rm -rf'

Just show the commands as commands; aliasing mechanisms may differ
from shell to shell, and some people don't know what aliases are.

-Karl

-- 
Subversion support & consulting  <>  http://producingoss.com/consulting.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org