[coreboot] gerrit: patch iterations in email [was: differences between patchset iterations]

Patrick Georgi patrick at georgi-clan.de
Tue Jan 29 09:01:43 CET 2013

Am 2013-01-28 23:54, schrieb David Hendricks:
> - Should we continue to have gerrit send e-mails for every patch 
> iteration?
Option 2: create a new mailing list, subscribe everyone over there by 
default, and let people unsubscribe if they don't want it. Downside: 
People with filter rules get commit messages in the inbox.

> - Can we remove the hash from the "Patch set updated" e-mails so they
> appear in a single thread?
Mail headers should be enough - I'll look into it.

>  - 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?
rebase: is a code change
inserting commit in a series: is a code change

It helps for developers to create "upstream branches" that contain 
_only_ the subset of interdependent changes. There is no other way for a 
tool to know which change is relevant and which is not, and it avoids 
updating 15 patchsets just because one commit has changed (which might 
have nothing to do with everything else).


More information about the coreboot mailing list