Hi all,
first of all, many thanks to JiHO for his detailed email. I wholeheartedly agree with everything he said, especially the part about git being useful for everyday, small and non-programming-related projects (I would have been completely lost hadn't I used it for my master's thesis).
Yes, but I would consider things like a two-stage commit process more focused on people who review lots of changes and do partial commits on those changes rather than those who do small changes on a personal branch. I think that a tool can be associated with what it makes easy, and I think that git makes it easier to do large projects with a distributed web of trust. Which is more a description of the kernel than Inkscape. It doesn't mean git can't do it, just more what it's targeted to.
In my experience, git is pretty much targeted to any application I've used it for. Maybe it's *also* targeted towards large projects structured like the kernel project, but it's certainly not *limited* to those and IMHO it's equally targeted to any other use case. Regarding the two-stage commits: I use them a lot even for my work on Inkscape, even for small commits, and I still find them very useful.
But again, much of what I said above probably also applies to other DVCS. I certainly don't want to start a flame war, I just want to point out that git is not the untameable beast it used to be (or at least it used to appear) and that it might fit our workflow just as well as bzr or any other DVCS.
Max