I've had the opposite experience — for me, Versions handles external modifications smoothly. Whether I'm working from Terminal, Xcode, or via ssh, Versions picks up changes pretty quickly, and doesn't crash for me.
Regardless of which tool you use, Subversion actually locks a working copy when commands which modify it take place, such as update, commit, and switch. If Versions attempts to access a working copy while it's locked, that status is displayed in the browsing view table. - Quinn On Sep 13, 2010, at 11:46 AM, Cue wrote: > I would shut down versions just incase. I'm not entirely sure what it does > when it initiates on start up but better to be safe than sorry. Versions has > a habit of choking when modifications are made to the working copy outside of > it's application. > > On 13 Sep 2010, at 19:10, Niels <[email protected]> wrote: > >> noob question: if I am going to execute some svn commands from the >> shell (ssh'ing in to fix something), do I need to shut down Versions >> first?
smime.p7s
Description: S/MIME cryptographic signature
