public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Greg KH <greg@kroah.com>
Cc: "George G. Davis" <gdavis@mvista.com>,
	<linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	<torvalds@linux-foundation.org>, <stable@kernel.org>,
	<jason.wessel@windriver.com>, Andi Kleen <andi@firstfloor.org>,
	<lwn@lwn.net>
Subject: Re: Announcement: Plans for v2.6.34-longterm
Date: Thu, 10 Nov 2011 15:29:01 -0500	[thread overview]
Message-ID: <4EBC340D.10806@windriver.com> (raw)
In-Reply-To: <20111110195411.GA11357@kroah.com>

On 11-11-10 02:54 PM, Greg KH wrote:
> On Tue, Nov 08, 2011 at 10:20:37PM -0500, Paul Gortmaker wrote:
>> [Re: Announcement: Plans for v2.6.34-longterm] On 08/11/2011 (Tue 15:52) Greg KH wrote:
>>
>> [...]
>>
>>> Also, I would like to populate the linux-stable.git tree with the
>>> missing .34-longterm releases that you have already done, care to
>>> provide a git tree that I can pull from for those now?
>>
>> Hi Greg,
>>
>> The below pull rq should get your repo caught up on the .34
>> content for my tags 8 --> 10.  You should be able to use the
>> "git verify-tag v2.6.34.10" on this older content without issue
>> as a double check on things.
> 
> $ git verify-tag v2.6.34.10
> gpg: Signature made Sun 26 Jun 2011 09:47:42 AM PDT using DSA key ID 0D0A18AD
> gpg: Good signature from "Paul Gortmaker (work) <paul.gortmaker@windriver.com>"
> gpg: Note: This key has expired!
> Primary key fingerprint: 2A15 067C 2C4D F8FD A89E  1882 DBE2 2294 0D0A 18AD
> 
> So I know that this was signed with an exprired key that is only
> self-signed, hm, looks like that matches up with the previous releases
> form you :)
> 
> thanks, now pushed out.
> 
> Hopefully you have a new key, that is in the kernel.org ring of trust,
> that you will be using to sign your new releases?

Yes, of course.  That is why the old one was recently expired.

P.

> 
> thanks,
> 
> greg k-h

  reply	other threads:[~2011-11-10 20:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 21:07 Announcement: Plans for v2.6.34-longterm Paul Gortmaker
2010-12-04 17:27 ` Greg KH
2010-12-05  0:45   ` Paul Gortmaker
2010-12-04 17:28 ` Greg KH
2010-12-05  1:16   ` Paul Gortmaker
2010-12-05 16:50     ` Greg KH
2010-12-06  4:54       ` Bruce Ashfield
2010-12-06  5:35   ` Minchan Kim
2010-12-06  6:01     ` Minchan Kim
2011-11-08 22:14 ` George G. Davis
2011-11-08 23:11   ` Paul Gortmaker
2011-11-08 23:52     ` Greg KH
2011-11-09  3:20       ` Paul Gortmaker
2011-11-10 19:54         ` Greg KH
2011-11-10 20:29           ` Paul Gortmaker [this message]
2011-11-09 17:12     ` George G. Davis

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=4EBC340D.10806@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=gdavis@mvista.com \
    --cc=greg@kroah.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=stable@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