For other developers: Please don't look at comments like the above and think that you are doing something wrong. Git is a tool, like any others, and you can be a good programmer using it in the way that makes you most productive.
Make small commits, make descriptive commits, whatever.
I don't think it's that simple when you're collaborating with others on a large project. I think Wine [0] is a great example of how small and atomic commits can create a very nice history that allows to you track down weird regression without having to read 1000+ SLoC commits or bunch of "chaff" that is just noise when you're trying to understand the bug. But it requires effort both from the developer to make actually good commits and from the maintainer to enforce these rules.
Make small commits, make descriptive commits, whatever.