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] first round of SCSI updates for the 6.7+ merge window
Date: Thu, 11 Jan 2024 14:47:45 -0800 [thread overview]
Message-ID: <CAHk-=wiHCkxrMCOL+rSGuPxUoX0_GSMLjgs9v5NJg6okxc1NLw@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=whKVgb27o3+jhSRzuZdpjWJiAvxeO8faMjHpb-asONE1g@mail.gmail.com>
On Thu, 11 Jan 2024 at 14:36, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Stop making a bad pgp experience even worse - for no reason and
> absolutely zero upside.
Side note: even getting gpg to show the subkeys was just an exercise
in frustration.
For example, I'd expect that when you do
gpg --list-key E76040DB76CA3D176708F9AAE742C94CEE98AC85
it would show the details of that key. No, it does not. It doesn't
even *mention* that key.
Because this is gpg, and the project motto was probably "pgp was
designed to be hard to use, and by golly, we'll take that to 11".
And no, adding "-vv" to get more verbose output doesn't help. That
just makes gpg show more *other* keys.
Now, obviously, in order to actually show the key I *asked* gpg to
list, I also have to use the "--with-subkey-fingerprint". OBVIOUSLY.
I can hear everybody go all Homer on me and say "Well, duh, dummy".
So yes, I realize that my frustration with pgp is because I'm just too
stupid to understand how wonderful the UX really is, but my point is
that you're really making it worse by using pointless features that
actively makes it all so much less usable than it already is.
Subkeys and expiration date make a bad experience worse.
Yes, I blame myself for thinking pgp was a good model for tag signing.
What can I say? I didn't expect people to actively try to use every
bad feature.
Linus
next prev parent reply other threads:[~2024-01-11 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 20:48 [GIT PULL] first round of SCSI updates for the 6.7+ merge window James Bottomley
2024-01-11 22:36 ` Linus Torvalds
2024-01-11 22:47 ` James Bottomley
2024-01-11 22:53 ` Linus Torvalds
2024-01-11 22:47 ` Linus Torvalds [this message]
2024-01-11 23:28 ` James Bottomley
2024-01-11 23:50 ` Linus Torvalds
2024-01-12 14:27 ` Konstantin Ryabitsev
2024-01-12 18:34 ` Linus Torvalds
2024-01-11 22:57 ` 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-=wiHCkxrMCOL+rSGuPxUoX0_GSMLjgs9v5NJg6okxc1NLw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).