Whether or not this makes sense depends on how you manage your commmits. For many projects, I think the changelog would produce too much noise. I would argue that your users care mostly about three things: what bugs were fixed, what new features are available, and any backwards incompatible changes. This can be hard to quickly glean from the commit history.<p>That said, if your history works with this model, then it's a handy tip :)