From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
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 4.14+ merge window
Date: Wed, 31 Jan 2018 12:16:36 -0800 [thread overview]
Message-ID: <1517429796.3344.10.camel@HansenPartnership.com> (raw)
In-Reply-To: <CA+55aFy4YfNEKiDipUXM_KYR5wen-8hmOp7B7t+=boq14EgdJA@mail.gmail.com>
On Wed, 2018-01-31 at 11:29 -0800, Linus Torvalds wrote:
> On Wed, Jan 31, 2018 at 9:42 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-
> > misc
>
> Ok, now I did indeed get that
>
> gpg: Can't check signature: unknown pubkey algorithm
>
> because of your fancy new key. But making git use gpg2 indeed fixes
> it, since I have a recent enough version.
>
> Let's see if anybody else even notices. I don't think lots of people
> look at the signatures.
Great! thanks for being the guinea pig. At least we know the theory is
now tested.
Regards,
James
next prev parent reply other threads:[~2018-01-31 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 17:42 [GIT PULL] first round of SCSI updates for the 4.14+ merge window James Bottomley
2018-01-31 19:29 ` Linus Torvalds
2018-01-31 20:16 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-11-14 16:36 James Bottomley
2017-11-15 0:33 ` Linus Torvalds
2017-11-15 9:35 ` James Bottomley
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=1517429796.3344.10.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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