"Partial Commits" are not needed to share code. That is why you use branches in Subversion: to provide a place for people working on a common development thread to put their work when it isn't ready for trunk.
You still stick to "only commit when green". No broken code goes into the repository. Branching and merging in Subversion is fraught with peril, it's better in the long run to use git. Subversion keeps track of versions of documents, and merging involves you making decisions about which version of a document is more recent. Git tracks diffs between documents, so merging branches is simply a case of collecting all the changes together in one place. It is quite possible to use git-svn to do local (ie: on the developer's workstation) "non-green" commits in case someone wants to try different ways of not solving a problem. The only catch is to remember to track a branch on subversion using it's own specific branch in the git repository, and only use rebase to bring patches in and out to the other git branches into that svn-tracking branch. When you share a patch you will branch from trunk, write the patch on that branch, merge that in with trunk. Just keep in mind that subversion deals in versioning entire documents, while git tracks changes you make. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
