mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 3.4+ merge window
Date: Tue, 22 May 2012 16:49:36 +0100	[thread overview]
Message-ID: <1337701776.2932.15.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <CA+55aFzHVEph_MvPjb=QiK4bg8qBDmdpzkXS4C1RCFyBDj6ecg@mail.gmail.com>

On Tue, 2012-05-22 at 08:44 -0700, Linus Torvalds wrote:
> On Tue, May 22, 2012 at 12:21 AM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >
> > You probably need to do a gpg --refresh
> >
> > I use the subkeys method for signing, so I have my master key (which
> > expires in 2016) in one of Greg's GPG devices, but I have signing and an
> > encryption subkeys which are short lived (currently expire in Oct 2012).
> > If you do a gpg --list-keys 'James Bottomley' you'll see this:
> 
> Ayup, that fixed it. Really confusing how it doesn't even show the
> signing key expiry date if you just look at the key ID..

If you find *that* the only confusing thing about gpg, we'll award you
the gold star grand master of expertise in it.  When my subkeys expired,
it took me a day to figure out from the error message I got trying to
sign something what the problem actually was.

James



      reply	other threads:[~2012-05-22 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 11:30 James Bottomley
2012-05-22  0:52 ` Linus Torvalds
2012-05-22  7:21   ` James Bottomley
2012-05-22 15:44     ` Linus Torvalds
2012-05-22 15:49       ` James Bottomley [this message]

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=1337701776.2932.15.camel@dabdike.int.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

all inboxes | Powered by JetHome®