The release notes are meant to list only noteworthy updates in a concise
manner. With 100-200 topics graduating to 'master' in each release cycle,
I cannot describe everything that happened in the release and expect the
result to be readable by the target audience, so we need to draw a line
somewhere. Usually miniscule details that affect no user in practice in a
real way are not described (e.g. "fix grammar in an error message").
Interested parties can always look at "git shortlog v1.7.6..v1.7.7".