Cleanup? Surely not.

I use sparse checkouts and a from-the-project-root checkout of Subversion.
A few moments ago, in one shell window, I did this (to fix some WC
bustedness due to recent but in property handling):

   # de-telescope, then re-telescope the 1.6.x directory
   cd projects/subversion/branches
   svn up --set-depth exclude 1.6.x; svn up 1.6 --force

Meanwhile, in another part of the working copy (the trunk), I was running
'svn st' in a loop. 'svn st' didn't care so much about the concurrent
de-telescope bit, but while the re-telescoping was happening, 'svn st'
produced the following:

$ svn st
subversion/svn/status-cmd.c:326: (apr_err=155037)
subversion/svn/util.c:959: (apr_err=155037)
subversion/libsvn_client/status.c:300: (apr_err=155037)
subversion/libsvn_wc/node.c:193: (apr_err=155037)
subversion/libsvn_wc/wc_db.c:4439: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:540: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:268: (apr_err=155037)
subversion/libsvn_wc/wc_db_pdh.c:101: (apr_err=155037)
svn: Previous operation was interrupted; run 'svn cleanup'
$

That seems like an odd error to me. No 'cleanup' was required -- when the
'svn up 1.6.x --force' completed, all was well. But I have no better
suggestions, and perhaps things are supposed to work this way. So I guess
this is a drive-by. :-)

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand