mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
	dan.j.williams@intel.com
Subject: Re: [GIT PULL] XArray updates
Date: Sat, 24 Nov 2018 19:00:23 -0800	[thread overview]
Message-ID: <20181125030023.GC3065@bombadil.infradead.org> (raw)
In-Reply-To: <CAHk-=whU1RMvzGvCwq8HaApYZuJ4STyfAYC5b_qDPFTwcTWD=Q@mail.gmail.com>

On Sat, Nov 24, 2018 at 06:49:30PM -0800, Linus Torvalds wrote:
> On Sat, Nov 24, 2018 at 6:38 PM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > I generated a new key 5EC42E41545C1F5E and signed a new tag
> > xarray-4.20-rc4
> 
> Hmm. Did you publicize it on any keyservers? I'm not finding the key
> on pgp.mit.edu or on the sks-keyservers.net pool..

I pushed it out to hkps://hkps.pool.sks-keyservers.net ... as I recall,
pgp.mit.edu is frequently not synchronised well with the other keyservers,
but I'm surprised that one of the sks-keyservers didn't have it.

http://pgpkeys.uk:11371/pks/lookup?search=0x5EC42E41545C1F5E&fingerprint=on&op=index

sees it just fine.

> > I've signed that key with my old DSA key 2218C81E8E7C03FF which has
> > about 400 signatures on it, but I understand is not terribly trustable
> > these days.
> 
> .. but at least I can find that one.  I think a 1024-bit DSA key may
> be borderline in theory, but it's a lot better than no key at all.
> 
>                Linus

  reply	other threads:[~2018-11-25  3:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-24 17:32 Matthew Wilcox
2018-11-24 18:04 ` Linus Torvalds
2018-11-25  2:38   ` Matthew Wilcox
2018-11-25  2:49     ` Linus Torvalds
2018-11-25  3:00       ` Matthew Wilcox [this message]
2018-11-25  3:07         ` Linus Torvalds
2018-11-25 17:45 ` 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=20181125030023.GC3065@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®