But on second thought, this still wouldn’t be equivalent to the git workflow described. I don’t know how you’d go about emulating it using svn (can anyone explain?).

Given that you know you want a particular workflow, the important question is how far does one tool facilitate it compared to the other.

I don’t know how tricky is it to commit to multiple repositories from the same working directory using svn (which i think would be necessary to approximate the effect of being able to commit locally and then push to a remote server at a later date). Or to take another example, how straightforward is it to update the same working directory from multiple different repositories.

These aren’t rhetorical questions; they’re things I’d never done with svn and don’t know if they’re possible–while i know they’re simple to do with git (great for working on the train!).

“I’d actually like to see some svn/git comparisons, but so far they’ve been from people on one side who seem not to understand the other.”

I’m certainly not the best person to try to provide a proper comparison between the two, but for what it’s worth, it does seem that a good proportion of git users used to be subversion users (myself included), while the opposite is not the case. Though i have seen a few posts from svn users switching to git and being confused (and angry), which i can relate to.

I’d actually like to see some svn/git comparisons, but so far they’ve been from people on one side who seem not to understand the other. Oh, well — I’ll be playing with both because now I’m running across more people using Git, so maybe eventually I can compare. ;)

That was me saying “It’s like coming up for air not to having to rely on there being an internet connection every time you want to commit.” on the monome forum.

You’re right that this doesn’t necessarily have to be the case, but it has been the case with all svn projects that i’ve worked on that the repository i need to commit to is not a local one, of course ymmv. A typical git arrangement seems to have a different workflow in this regard; there’s still a remote repository, but you have a local mirror of it too. You commit frequently to your local repos, and periodically push to the remote repos.

“Since the change log is a mile long, I’ll point out an obscure new power-user feature in Max 5.0.6.

You can send a new message to Max like this (or put it in an init file):
;max sortpatcherdictonsave 1

This makes it so that the JSON files that are use by Max for saving patches will keep the dictionary in the same order (alphabetized) every time you save. If you are keeping your patches in version control (e.g. SVN, GIT, CVS, etc.) then this should make your diffs a lot more usable.”

Haven’t tried it yet but sounds very promising!