On 07/29/2013 03:30 PM, Rafael J. Wysocki wrote: > On Monday, July 29, 2013 02:17:34 PM John W. Linville wrote: >> On Mon, Jul 29, 2013 at 03:27:44PM +0200, Rafael J. Wysocki wrote: >> >>> That said we have the same issue with commits with just two SOB tags if >>> a maintainer applies a patch that nobody has responded to. Are they going >>> to >>> be regarded as "suspicious" too now? >>> >>> And what about trusting maintainers? If Linus trusts them enough to pull >>> from >>> them, why can't everybody else trust them enough to assume that they don't >>> do >>> bad things on purpose? >> >> Not just Linus -- it's 'turtles all the way down' here. As someone >> else suggested, a Singed-off-by in the merge commit should suffice >> here. Although, I haven't always made a habit of adding S-o-b to >> merge commits either... > > An SOB in the merge doesn't provide any additional information that can't > be retrieved from git, unless you use a different e-mail address for the > sign-off. :-) >
Watch out for fast forward merges. Ideally I guess maintainers really should disable fast forwards and PGP-sign their merge commits... -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/