From: Jonathan Corbet <corbet@lwn.net>
To: Laszlo Ersek <lersek@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH 2/7] Docs: Bring SubmittingPatches more into the git era
Date: Wed, 9 Mar 2016 07:13:09 -0700 [thread overview]
Message-ID: <20160309071309.36141068@lwn.net> (raw)
In-Reply-To: <56E00C9A.4060703@redhat.com>
On Wed, 9 Mar 2016 12:44:26 +0100
Laszlo Ersek <lersek@redhat.com> wrote:
> Namely, do signed tags serve the purpose that a higher level maintainer
> can pull from a trusted, lower level maintainer without looking?
>
> At these higher levels of the patch flow, does "trusted identity"
> replace "review"?
No, I really don't think so. Signed tags just verify the origin of the
pull request.
Think of it as a form of defense in depth. Anybody who merges code into
the kernel merges bugs on a regular basis, even if they carefully review
every line. Review is a defense against threats like the deliberate
insertion of malevolent code, but it is not an absolute defense. Signed
tags, one might hope, will at least keep code from deliberately forged
pull requests out of the stream of code needing review.
Or so I see it.
jon
next prev parent reply other threads:[~2016-03-09 14:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 16:32 [PATCH v2] Docs: Modernize SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 1/7] Docs: Remove "tips and tricks" from SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 2/7] Docs: Bring SubmittingPatches more into the git era Jonathan Corbet
2016-03-09 9:45 ` David Woodhouse
2016-03-09 11:44 ` Laszlo Ersek
2016-03-09 14:13 ` Jonathan Corbet [this message]
2016-03-09 14:04 ` Jonathan Corbet
2016-03-09 14:27 ` David Woodhouse
2014-12-23 16:32 ` [PATCH 3/7] Docs: Update recipient information in SubmittingPatches Jonathan Corbet
2014-12-23 16:32 ` [PATCH 4/7] Docs: SubmittingPatches: update follow-through instructions Jonathan Corbet
2014-12-23 16:32 ` [PATCH 5/7] Docs: SubmittingPatches: miscellaneous cleanups Jonathan Corbet
2014-12-23 16:32 ` [PATCH 6/7] Docs: Mention device tree binding info Jonathan Corbet
2014-12-23 16:32 ` [PATCH 7/7] Docs: SubmittingPatches: mention using pull requests as a cover letter Jonathan Corbet
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=20160309071309.36141068@lwn.net \
--to=corbet@lwn.net \
--cc=dwmw2@infradead.org \
--cc=lersek@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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