| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 29 Jul 2013 14:17:34 -0400 From: "John W. Linville" <linville@...driver.com> To: "Rafael J. Wysocki" <rjw@...ysocki.net> Cc: Jason Cooper <jason@...edaemon.net>, Samuel Ortiz <sameo@...ux.intel.com>, ksummit-2013-discuss@...ts.linuxfoundation.org, Linus Torvalds <torvalds@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process 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... John -- John W. Linville Someday the world will need a hero, and you linville@...driver.com might be all we have. Be ready. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists