<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Lately I have observed <a href="http://trac.webkit.org/changeset/111595">more</a> and <a href="http://trac.webkit.org/changeset/111577">more</a> and <a href="http://trac.webkit.org/changeset/111527">more</a> changes going into WebKit that lack any details about why a particular change was made. It is intended that the ChangeLog (and commit message) contain some details about your change, not just the bug title and URL.</div><div><br></div><div>The <a href="http://www.webkit.org/coding/contributing.html#changelogs">contributing information</a> on subject is pretty sparse, which has likely caused this problem to manifest. However, the <a href="http://trac.webkit.org/changeset/43259">example ChangeLog</a> linked from that page is prime example of what we all should strive for when describing our changes.</div><div><br></div><div>To help curb this lack of detail in ChangeLogs, I <a href="https://bugs.webkit.org/show_bug.cgi?id=81828">propose we add script</a> (or augment an existing script) to check for this missing information and inform the contributor. It is clear not all reviewers are asking patch authors to provide this information when reviewing, and such a tool would help enforce it.</div><div><br></div><div apple-content-edited="true">
— Timothy Hatcher<br><br></div></body></html>