Comments on: Working with Subversion http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/ up to the minute updates Sat, 22 Nov 2008 11:37:04 +0000 http://wordpress.org/?v=2.2 By: Daniel http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-25866 Daniel Mon, 03 Mar 2008 06:47:10 +0000 http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-25866 Appreciate the article! I got the following error when I followed your instructions: <code> bash: line 1: svnserve: command not found svn: Connection closed unexpectedly </code> What solved it was creating a file called .bashrc in the home directory of my test server and adding the following line: <code> PATH=$PATH:/usr/local/bin </code> Good luck! Appreciate the article!

I got the following error when I followed your instructions:

bash: line 1: svnserve: command not found
svn: Connection closed unexpectedly

What solved it was creating a file called .bashrc in the home directory of my test server and adding the following line:

PATH=$PATH:/usr/local/bin

Good luck!

]]> By: Ray http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-16139 Ray Wed, 31 Oct 2007 19:41:24 +0000 http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-16139 To deal with the local vs production config problem, I create a parallel branch to hold my local versions of config files, then do a svn copy of the config files into the branch, svn switch my working copy to the branched version, then do my local changes and commit. This way, when you commit, it commits to the branch, not the trunk, so the trunk version stays a good copy of the production setup. If you need to make changes to both your local and production config files, make them and do a svn merge to keep them in sync. Does that make any sense? To deal with the local vs production config problem, I create a parallel branch to hold my local versions of config files, then do a svn copy of the config files into the branch, svn switch my working copy to the branched version, then do my local changes and commit. This way, when you commit, it commits to the branch, not the trunk, so the trunk version stays a good copy of the production setup. If you need to make changes to both your local and production config files, make them and do a svn merge to keep them in sync. Does that make any sense?

]]> By: 3stripe http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-12859 3stripe Sun, 22 Jul 2007 13:49:11 +0000 http://blog.circlesixdesign.com/2007/04/13/working-with-subversion/#comment-12859 Great article! I've just started learning Subversion and all the how-to's on your blog have been a massive help. Cheers, 3stripe Great article!

I’ve just started learning Subversion and all the how-to’s on your blog have been a massive help.

Cheers, 3stripe

]]>