On 28/08/10 16:21, C Anthony Risinger wrote: > On Aug 28, 2010, at 9:12 AM, Johannes Held <mail@xxxxxxxxx> wrote: >> git does really support my way of coding. BUT perhaps I've changed >> my style of >> coding to match git? Who knows. … > > The thing I think people have the most problems with is the fact that > git is less of a VCS itself, and more of a _toolkit_ to design your > own workflow. It originally was, and very much still is, a simple > content addressable datastore, that happens to have some conveinence > layers making it a good DVCS. Which is one of the main reasons why I personally avoid git. I want a *VCS*, not a *toolkit*. :-) Every single VCS I've used have had the same basic workflow. Then they add some stuff on top, and very few end up being unusable (though there are some notable exceptions). Git is *extremely* flexible, and allows for custom workflows, just like you mention. However, I suspect that about 95% of all projects using git doesn't actually need the flexibility. My recommendation is always to choose something other than git if you can get away with it, but choose something that allows you to migrate to git without too much difficulty. Then it's possible to move to git once it's really needed. There aren't that many who listen to me though. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
Attachment:
signature.asc
Description: OpenPGP digital signature
