Switching & Unversioned Files

Hey all -

I'm hoping someone has some practical suggestions. I have a code base
with upwards of 2500 files. Not huge by any means, but also not
trivial. When my working copy is operational, though, there are a
number of unversioned files that exist within the code base. Some are
configuration files, some are files created by the application itself,
etc.

What I've been noticing is that I don't seem to be able to switch
branches effectively and, as far as I can tell, it's because of the
unversioned files. What I end up with is a number of directories
which are switched the the targeted branch and others that are not.
This has caused issues with code being committed to the wrong branch
and other such fun.

It makes sense that switching is affected by unversioned files since
svn has no way of knowing how to handle them, but is there anything I
can do to validate that a switch was complete? Is there any way to
do...an "atomic" switch, perhaps?

Any suggestions would be appreciated.

Thanks.

-- 
Rob Wilkerson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org