You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by marvin greenberg <mg...@dctd.No.spam.saic.com> on 2004/03/08 00:53:26 UTC
Re: [Issue 1751] svn switch may corrupt working copy
julianfoad@tigris.org wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1751
>
Is there a work-around to this issue? I've seen this problem but don't really
understand from the issue when it will happen and when it won't.
We were planning to use 'svn switch' as part of our process for merging between
branches. But obviously that won't work if it it corrupts the WC...
marvin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1751] svn switch may corrupt working copy
Posted by Ben Collins-Sussman <su...@collab.net>.
On Sun, 2004-03-07 at 18:53, marvin greenberg wrote:
> julianfoad@tigris.org wrote:
> > http://subversion.tigris.org/issues/show_bug.cgi?id=1751
> >
>
> Is there a work-around to this issue? I've seen this problem but don't really
> understand from the issue when it will happen and when it won't.
>
> We were planning to use 'svn switch' as part of our process for merging between
> branches. But obviously that won't work if it it corrupts the WC...
I don't think you need to be afraid of 'svn switch'. We've all been
using it for years. Gstein seems to have found an edge case
specifically related to using the '-N' (--nonrecursive) option with
checkout and switch. The -N flag is pretty rarely used, and already has
known bugs, so I'm not surprised.
As long as you stay way from -N, you should be just fine.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org