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

Re: [TSVN] Feature Request: Make switches safer.

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2005-09-06 18:36:46 CEST

Greg Stevenson wrote:
> Saw that moving/copying was made safer so I thought I would ask for this. I
> found that bad things happen if a switch is done and folders need to be
> removed.
> For example: 1.0 has the subfolders Common and Source. 2.O added the folder
> DB. If someone is working in 2.0, commits, and wants to switch to 1.0 the
> switch abruptly aborts if the DB folder cannot be removed because some app
> is open that has a lock on the folder even if it has no open files or one or
> more uncontrolled files exist in the folder. This leaves the working folder
> in a very undefined state. Delete and Checkout is the safest course of
> action at this point. Having at least a precheck and aborting before taking
> action with a warning would be nice.

- the switch is done by the Subversion library. TSVN doesn't do the
switch itself.
- So TSVN doesn't know which files/folders are really affected by the switch
- Even if TSVN knew (we could just guess), the check wouldn't really be
accurate: a file/folder could be locked during the check but not be
locked shortly afterwards, or it could *not* be locked, but then it
could be in use by another program when the actual switch happens.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 6 18:37:10 2005

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