Discuss: Collaborate and Connect with Subversion
by Ryan Irelan
- Editorial Comments
2 Obsolete?
Only a small part of the world has moved on to git, mostly Mac-based developers. The lack of a decent desktop client on Windows or requiring cygwin to use git at all is proof of that and means that there’s a larger barrier to entry for the the much larger development community that still works off Windows.
posted at 02:55 am on July 2, 2008 by Jonathan_Snook
3 SVN is not obsolete
Subversion certainly is not obsolete – it’s still the best free solution for Windows in terms of community and support.
I’m also surprised that this article didn’t mention TortoiseSVN, an excellent Windows GUI for managing your files in Subversion. It integrates directly into Windows and lets you access your Subversion repository like any other Windows folder.
posted at 03:07 am on July 2, 2008 by Geoffrey Lee
4 Great Idea
I certainly never thought of using SVN to work with my freelance writing clients. This is just completely blowing my mind how I never saw to use it that way.
posted at 03:19 am on July 2, 2008 by Zac Davis
5 SVN not obsolete, but certainly not cutting edge
While I would like for Git to be the mainstream way to collaborate on projects, SVN is still the standard.
I am somewhat surprised by the number of great looking tools popping up for SVN ( Versions & Cornerstone ) since it does seem (from a Git user’s perspective) to be on the way out.
One of the great things about Git is that you can use it with SVN repositories. I use Git every day with SVN projects and nobody else on my team has to know that I get all the benefits of Git while using the same old repository. Forking, branching, and merging are wonderful things.
posted at 04:08 am on July 2, 2008 by Trey Piepmeier
6 Agreed on Git (or any other DVCS)
Once you start easing into the branchy workflow, you’ll never want to go back to Subversion. Subversion made branches cheap; Git makes merges cheap, and there is a world of difference there.
I wouldn’t call Subversion obsolete, though. But I also wouldn’t call Git fringe.
posted at 04:18 am on July 2, 2008 by Edward Yang
7 Bazaar is nice too
Another distributed version control system worth looking at is Bazaar . It is very easy to install on windows (and other platforms of course). Its developers have paid a lot of attention to accommodating different workflows, and I think it definitely succeeds at being more flexible than subversion, and probably the others too.
I had used SVN previously, and recently evaluated several version control systems for my lab group, and ended up choosing Bazaar because I like its philosophy and I found it to be the easiest system to get up and running on our server.
posted at 04:37 am on July 2, 2008 by Jason Merrill
8 Untitled
I never considered using GIT so far. Might be a good idea to take a closere look.
posted at 04:38 am on July 2, 2008 by a gatt
9 Untitled
I never considered using GIT so far. Might be a good idea to take a closere look.
posted at 04:40 am on July 2, 2008 by a gatt
10 Git and Subversion
Git on Windows doesn’t need cygwin alone anymore, it’s possible to use msysgit, with nice gui and terminal. It’s in beta but will be part off the official git soon.
And it’s no problem to work with Git and Subversion over git-svn.
I tried Mercurial and Bazaar, too. But git is my favourite. Subversion is complicated, inconvenient and insecure (files can easily get corrupt). With git all you need is a “git init” and your repo is working. Locally, no need for server configuration.
posted at 08:16 am on July 2, 2008 by Stefan Imhoff
Got something to say?
Discuss this article. We reserve the right to delete flames, trolls, and wood nymphs.
Create a new account or sign in below if you’d like to leave a comment.
Subscribe to this article's comments: RSS (what’s this?)



1 Subversion is obsolete - you want something like g
While the basic points about needing a version control system are sound, subversion itself is obsolete. The world has moved on to distributed version control systems like git (or perhaps mercurial).
Certainly you wouldn’t start a new project using subversion – it’s only appropriate for legacy setups where making a switch to a modern setup needs to be delayed for some reason.
posted at 02:22 am on July 2, 2008 by James Moore