<div dir="ltr">Necromancing this thread.<div><br></div><div>There seems to be a bit of frustration regarding the noise caused by some recent patch sets. A quick look at the <a href="http://www.coreboot.org/pipermail/coreboot/2013-January/thread.html" target="_blank">January mailing list archive</a> shows how messy things are at the moment.</div>
<div><br></div><div>In the beginning it seemed like most people preferred to rely on e-mail filters to filter out excessive noise. But due to recent comments, I'm curious if it's worth re-visiting some ideas we discussed earlier about frequency and style of patch update notifications:</div>
<div>- Should we continue to have gerrit send e-mails for every patch iteration?<br></div><div>- Can we remove the hash from the "Patch set updated" e-mails so they appear in a single thread?</div><div>
- Is there a way to make gerrit *not* send update notifications if no actual code changes were made, for example if the patch was inserted into a series or if the commit message was changed?</div><div>- Can we make Jenkins send less verbose messages to the IRC channel so that it sends out one (instead of two) brief messages indicating a patch's success or failure?</div>
<div><br></div><div>Any other thoughts?</div><div><br></div><div><div class="gmail_extra">-- <br>David Hendricks (dhendrix)<br>Systems Software Engineer, Google Inc.