Just do your team a favor and commit to a branch and then interactive-rebase-squash them into a few commits at the end. Some teams, mine included, have a contract that every commit should be in a runnable/semi-correct state so that git-bisect works correctly but committing each save would guarantee that this contract would not work.
In addition, how would you name the commits to be meaningful?
Have you considered using dropbox instead? We use Dropbox for those bad days when things just don't work, and we do try to commit about once an hour or so when we finish major milestones in a feature, but this means that the commits that we do make are really meaningful and historically important. Then to keep to the contract we squash them at the end into one commit. Our team is a little weird though and people much smarter than us don't do this; I know twitter doesn't squish commits for instance.
Thanks for bringing it up though! I think this is a fascinating topic and I'd love to hear where you go with it and what works for you!