versions and the command line
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? -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Re: versions and the command line
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 niels.ol...@gmail.com 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
Re: versions and the command line
Does Versions pick up changes smoothly when you delete something from your working copy outside of versions? If so, I must be doing something wrong. On 13 Sep 2010, at 19:52, Quinn Taylor quinntay...@mac.com wrote: 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 niels.ol...@gmail.com 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? -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
Re: versions and the command line
It does for me, but it doesn't mean you're doing something wrong. Are you talking about a filesystem delete or `svn delete` outside of Versions? For me, both cases work just fine. I'm on 10.6, but it works fine for me on 10.5 as well. - Quinn On Sep 13, 2010, at 3:47 PM, Cue wrote: Does Versions pick up changes smoothly when you delete something from your working copy outside of versions? If so, I must be doing something wrong. On 13 Sep 2010, at 19:52, Quinn Taylor quinntay...@mac.com wrote: 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 niels.ol...@gmail.com 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? -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en. smime.p7s Description: S/MIME cryptographic signature
Re: versions and the command line
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? I have always mixed matched command line and client (whether it's Versions or Xcode), without quitting. David Dunham http://a-sharp.com Twitter: @ASharpLLC -- You received this message because you are subscribed to the Google Groups Versions group. To post to this group, send email to versi...@googlegroups.com. To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/versions?hl=en.
