And I could double-click any commit and get the 'changeset details' with all the files modified and their diffs, but it's still better to provide an overview of what you're checking in instead of forcing people to interpret your code.
At my current job we have dev tasks associated with the changesets (if applicable), so that helps provide context also.
git log --pretty=oneline --abbrev-commit --graph --stat
Seeing the names of the changed files in each commit gives me a lot more of context than simply the commit description.