commit summaries.

I have been watching and using this project for a few years now, and really do love this API and you have done an amazing job on it. The one thing I really have to complain about, though, is the frigging commit summaries. Anybody who has slightly more than a beginner knowledge of source control knows that "modify it" is a not anywhere near an acceptable commit summary. Commit summaries are meant to give a short description of what's been modified and how. Looking at the commit list, I have no idea how much this project has evolved since I looked at it, what near features have been added, what bugs have been fixed, how the API has changed, etc. It gives me virtually no even remotely useful information. In source control and especially in open source projects like this, the commit summaries are actually important, so could you please consider giving slightly more detailed summaries (really, for your own sake more than more).

Sorry to have to be so tough on you, but this has been bugging more for a while.

The issue names no files, tests, or entry points. Start by reviewing the repository's commit history and any contribution guidance to understand the current summary conventions; done would mean an agreed, specific process for writing informative commit summaries.