Navigation
User login
Tags
needswork seo drupal.strategy api javascript jquery google facebook twitter greasemonkey drupal i18n internationalization translation ajax language module release svn versioncontrol upgrades drupalplanet core firefox ui gmtranslator strategy search drupalcon deployment configuration features distributions installprofile performance pressflow varnish drush_make aegir pantheon

I really (really) don't want
I really (really) don't want to turn this into a 'my SCM is better than yours' discussion but the problems mentioned above are (one of) the reasons why I've switched from SVN to Git. Git does require a bit of reading and a different way of thinking about version control but this (small) investment in time/effort really pays of in the end.
One possible way to use a vendor branch like approach with Drupal in Git:
http://versioncontrolblog.com/2007/08/02/upgrading-drupal-52-with-git/
I've been using SVN for quite some time and was rather reluctant to learn about Git (time is scarce :D) but in the end it was really worth it, especially when working with other developers or when using external components like Drupal.