git push and the reasons not to do it
Wed Feb 25 13:49:53 PST 2009
After this entry about the difference between push and pull for Mercurial, and how that doesn't fit with the way I instinctively want to use a repository, it's interesting to read Ted Tso responding to a similar complaint from a git user. Tso explains the discrepancy well:
Part of the problem here is that for most git workflows, most people don't actually use "git push". ....in most large projects, the number of people [who] need to use the "scm push" command is a very small percentage of the developer population, just as very few developers have commit privileges... Ah, but in a distributed SCM world, things are more democratic....While this is true, the number of people who need to be able to publish their own branch is small.... There is one exception to this, of course, and this is a developer who wants to get started using git for a new project which he or she is starting and is the author/maintainer, or someone who is interested in converting their project to git.
The whole entry, plus the comments, are worth reading.