Who started this thread seems to be a people that love finish his post with FACT!
Well, I have a FACT! for him:
1) when I have a young project I need to adjust many things several times. This means many commit. But this is more a proof that the project is still young that better than other project with less commit.
2) Looking to wayland, there are less commits now than in the past, this is because the project is more mature now, it's not because there are less developers now or less interest.
3) how can you manage the following situation:
Project A: sent a commit to change a variable name
Project B: sent a commit to implement a new feature
they are 1 commit for side, but do you think they have the same importance?
How your really-idiot-proof-of-gnome-kills-kde can address this kind of error?
Untill you can proof without doubts that the number of commits represent everything about the vitality of a project, you remain a troll.
And now go home. Bye.