Messages in this thread | | | Date | Thu, 10 Nov 2011 15:29:01 -0500 | From | Paul Gortmaker <> | Subject | Re: Announcement: Plans for v2.6.34-longterm |
| |
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
| |