Hi William,
Windows on git is indeed excellent, thanks to the Git Extensions project:
That is great to hear! Interesting also what you say about TortoiseGit (I would have thought it might come closest to the needs of people missing TortoiseSVN).
Being able to code fearlessly is liberating! Revision control should work with the natural creative flow, not interfere with it. Creativity is messy, though, and nobody wants to submit ugly commits like that. When I'm done coding a new feature, I'll use git's interactive rebase feature to go back and clean up the history, producing a few logical, well-formatted patches to submit upstream:
* Fix the loader bug * Add the new menu items
It's hard to describe how much better this workflow is. It's something that can only be experienced.
I completely and wholeheartedly agree. My workflow is quite similar to yours, and git's interactive rebase is one of the major things I miss in other version control systems. I know some people say that history should never be changed, but I want and need the freedom to create a right mess in my local repository :), with frequent commits where I can try different things and don't need to worry about whether that's the most sensible way to present them to the rest of the community. Being able to regroup them into nice and logical chunks before pushing, which will make sense to someone browsing the history even in a few months' or years' time is a major advantage and extremely liberating.
Cheers, Max