From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Bjorn Helgaas <helgaas@kernel.org>, Eric Wong <e@80x24.org>,
Han-Wen Nienhuys <hanwen@google.com>,
workflows@vger.kernel.org
Subject: Re: Lyon meeting notes
Date: Fri, 1 Nov 2019 21:46:24 +0100 [thread overview]
Message-ID: <CAMuHMdV0M4YrexhYdEH2wRkhB6gyTtMXigA4QfMjYO3BCysZUg@mail.gmail.com> (raw)
In-Reply-To: <20191101200755.h7gyt63rgwyxuqbd@pure.paranoia.local>
Hi Konstantin,
On Fri, Nov 1, 2019 at 9:10 PM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
> On Tue, Oct 29, 2019 at 06:13:13PM -0500, Bjorn Helgaas wrote:
> > On Tue, Oct 29, 2019 at 10:26:29PM +0000, Eric Wong wrote:
> > * Linus checks sigs, but subsystem maintainers don’t.
>
> Rather, they can't, because there is no accepted or workable mechanism
> for doing so.
That depends. The pull requests I send to subsystem maintainers use
signed tags, just like the ones I send to Linus.
The difference lies in the transport medium: Linus receives most commits
through (signed) pull requests, while most (leaf) maintainers receive
(non-signed) emailed patches.
> > * Identity tracking? PGP giving up on key signing. TOFU.
I guess TOFU is good enough for patch submissions.
Does it really matter who I am? Yeah, the DCO says I must use my real name.
But would people stop trusting my patches if I suddenly announced my name
is not (and has never been) Geert Uytterhoeven?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2019-11-01 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 15:41 Han-Wen Nienhuys
2019-10-29 22:26 ` Eric Wong
2019-10-29 23:13 ` Bjorn Helgaas
2019-11-01 20:07 ` Konstantin Ryabitsev
2019-11-01 20:46 ` Geert Uytterhoeven [this message]
2019-11-01 21:30 ` Theodore Y. Ts'o
2019-11-02 1:17 ` Eric Wong
2019-11-01 21:34 ` Dmitry Vyukov
2019-10-29 22:35 ` Daniel Axtens
2019-11-01 17:29 ` Konstantin Ryabitsev
2019-11-01 17:35 ` Dmitry Vyukov
2019-11-02 11:46 ` Steven Rostedt
2019-10-30 9:21 ` 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=CAMuHMdV0M4YrexhYdEH2wRkhB6gyTtMXigA4QfMjYO3BCysZUg@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=e@80x24.org \
--cc=hanwen@google.com \
--cc=helgaas@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=workflows@vger.kernel.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