I seem to recall that something like this was discussed recently on the list. While excluding commits on already updated branches works if the same set of recipients receive e-mails for both branches by eliminating the duplicates, I suspect that in more elaborate settings people would want to do different notices for different branches, and for that kind of usage people who subscribes only to branch1 in your picture would miss what happened on branch2. Or maybe branch1 is the main integration branch (e.g. 'master', 'next') while branch2 is a tentative topic that does not send out notification e-mails. If we want to take this example hook seriously, I suspect that the existing mechanism based on hooks.* variables might need to be made to allow finer grained, per-branch, control. I dunno. Post 1.5.0. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html