Some of these differences in numbers come from how git works in general.
A push is basically just uploading your repository to the remote server. As such a push might contain many commits by the person who pushes and others by different people - many of which are also part of other pushes.
Also due to the decentralized model of git and the model of pulling code from other people, it's highly likely that some (most?) of these pushes/commits never end up in the official repositories of the different projects.
Pushes may contain commits to throwaway branches, to branches for private use.
Also, the blog post doesn't say anything about rebases. If I push a rebased private branch, it will contain all the commits of the branch but with changed IDs.
There are so many more occasions for a commit to be moved around over the network in git than there is in the more centralized solutions as they are provided by Google Code and Sourceforge.
Yes. Google Code does provide Mercurial, but it's still project centric. So what gets committed to google code is official code that is part of that projects code base.
What gets commited to github is mostly throwaway stuff or patches about to be processed before being merged into some mainline.
This is where the difference comes from. It's just natural.
A push is basically just uploading your repository to the remote server. As such a push might contain many commits by the person who pushes and others by different people - many of which are also part of other pushes.
Also due to the decentralized model of git and the model of pulling code from other people, it's highly likely that some (most?) of these pushes/commits never end up in the official repositories of the different projects.
Pushes may contain commits to throwaway branches, to branches for private use.
Also, the blog post doesn't say anything about rebases. If I push a rebased private branch, it will contain all the commits of the branch but with changed IDs.
There are so many more occasions for a commit to be moved around over the network in git than there is in the more centralized solutions as they are provided by Google Code and Sourceforge.
Yes. Google Code does provide Mercurial, but it's still project centric. So what gets committed to google code is official code that is part of that projects code base.
What gets commited to github is mostly throwaway stuff or patches about to be processed before being merged into some mainline.
This is where the difference comes from. It's just natural.