[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 1751] svn switch may corrupt working copy

From: Marvin Greenberg <mgreenberg_at_dctd.saic.com>
Date: 2004-03-08 17:30:57 CET

> From: Ben Collins-Sussman <sussman@collab.net>
> Subject: [Issue 1751] svn switch may corrupt working copy
>
> 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.

If you look at the case, it specifically says it isn't just "-N". I have had
this happen doing really simple things like a switch from branches/br1 to
branches/br2. No -N flag, nothing fancy. Resulting in a wedged working copy,
with a rather painful process to recover, figure out what is changed (since all
sorts of svn commands like status and diff) don't work.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 8 17:32:19 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.