From: "H. Peter Anvin" <hpa@zytor.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
LKML <linux-kernel@vger.kernel.org>,
ksummit-2013-discuss@lists.linuxfoundation.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jason Cooper <jason@lakedaemon.net>
Subject: Re: [Ksummit-2013-discuss] [ATTEND] DT, maintainership, development process
Date: Tue, 30 Jul 2013 22:47:31 -0700 [thread overview]
Message-ID: <51F8A4F3.4020003@zytor.com> (raw)
In-Reply-To: <4053222.hWzinV5Hra@vostro.rjw.lan>
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
next prev parent reply other threads:[~2013-07-31 5:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130729102452.GA2682@zurbaran>
[not found] ` <alpine.LNX.2.00.1307291230270.18809@pobox.suse.cz>
2013-07-29 13:10 ` Rafael J. Wysocki
2013-07-29 14:11 ` Jonathan Corbet
2013-07-29 16:31 ` Paul Gortmaker
2013-07-29 16:33 ` Jiri Kosina
2013-07-29 22:09 ` Rafael J. Wysocki
2013-08-01 10:16 ` Geert Uytterhoeven
2013-08-01 17:40 ` Rafael J. Wysocki
[not found] ` <20130729113526.GB3604@zurbaran>
[not found] ` <20130729130357.GQ29916@titan.lakedaemon.net>
2013-07-29 13:27 ` Rafael J. Wysocki
2013-07-29 18:17 ` John W. Linville
2013-07-29 18:41 ` Jason Cooper
2013-07-29 22:30 ` Rafael J. Wysocki
2013-07-31 5:47 ` H. Peter Anvin [this message]
2013-07-31 5:56 ` James Bottomley
2013-07-31 11:48 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F8A4F3.4020003@zytor.com \
--to=hpa@zytor.com \
--cc=jason@lakedaemon.net \
--cc=ksummit-2013-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=rjw@rjwysocki.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®