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

Re: svn switch didn't switch enough - what did I do wrong?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-08-06 16:30:38 CEST

On Aug 6, 2005, at 9:04 AM, Scott Palmer wrote:
> Is there a reason for stopping outright in a situation like this?
> Could it not continue and do as much of the switch (or update) as
> possible and treat the problem area much like a conflict?

We don't handle tree conflicts. There are issues filed on this... as
old as the hills. Nobody's come up with a good design yet.

For example, when 'svn up/switch' wants to delete a file that has
local modifications, it just removes the file version control. The
file becomes unversioned. (A lot of people hate this, but then
they'd also hate it if the update stopped cold.) But what should
happen if the update wants to delete a directory containing
unversioned or edited data? Move it out of the way?

For more thoughts on the problem, see issues 2282 and even 563.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Aug 6 16:32:31 2005

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

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