All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] final round of SCSI updates for the 5.19+ merge window
Date: Sat, 13 Aug 2022 13:47:47 -0700	[thread overview]
Message-ID: <CAHk-=wgeVWg=3sae6u__x2dhMzxw2-nyTTkxbQZfkDrueXGvTg@mail.gmail.com> (raw)
In-Reply-To: <62ef6e3d028a5182f4485d6201a126bbf4ca659c.camel@HansenPartnership.com>

On Sat, Aug 13, 2022 at 5:55 AM James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
>
> [my key just expired so you'll need to do the dane update thing I
> showed you]

Oh, I don't care about expired keys at all. As long as you keep using
the *same* key, I'm happy, and gpg saying "Note: This key has
expired!" is something I'll happily ignore.

None of the technical rules of pgp keys make any sense at all. The
"sufficient trust" computations are completely pointless garbage with
the whole "marginal" vs "complete trust". It's all just crazy talk.

The expiry times likewise. I will completely ignore those.

I will check the signatures of a key as I import them. Because anybody
who thinks that "trust" is about automation is probably not human, or
so far on the spectrum that they don't understand humans.

              Linus

  reply	other threads:[~2022-08-13 20:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-13 12:55 [GIT PULL] final round of SCSI updates for the 5.19+ merge window James Bottomley
2022-08-13 20:47 ` Linus Torvalds [this message]
2022-08-13 21:48 ` pr-tracker-bot

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='CAHk-=wgeVWg=3sae6u__x2dhMzxw2-nyTTkxbQZfkDrueXGvTg@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.