public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Zankel <chris@zankel.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] xtensa patchset for 3.7
Date: Wed, 03 Oct 2012 15:59:11 -0700	[thread overview]
Message-ID: <506CC33F.4090308@zankel.net> (raw)
In-Reply-To: <CA+55aFyva3aWXBOBwERPJMyX+2LqydYs4Bq4ZBUPXZFMtPqZOg@mail.gmail.com>

Hi Linus,

On 10/03/2012 03:41 PM, Linus Torvalds wrote:
> That should be
>
>     git://github.com/czankel/xtensa-linux tags/xtensa-next-20121003
>
> which is the public git address of that server.
Sorry about that. I mistakenly used 'origin' instead of the actual address.

> However, you now do have a signed tag, but the key you have used for
> it is not available on any of the regular keyservers. Neither
> pgp.mit.edu nor keys.gnupg.net know about that key A1F191F0, which I
> assume also means that it's not actually signed by anybody else
> either.
>
> I see that you're based in St Petersburg, is there anybody around you
> can get your key signed with?
I'm actually located in the Bay Area (Max, who's helping out, is in St. 
Petersburg), and could stop by anywhere around here. I'll also try ask 
some old friends if they are still in the position to certify the signature.

Thanks,
-Chris


  reply	other threads:[~2012-10-03 22:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03 22:23 [GIT PULL] xtensa patchset for 3.7 Chris Zankel
2012-10-03 22:41 ` Linus Torvalds
2012-10-03 22:59   ` Chris Zankel [this message]
2012-10-03 23:07     ` Linus Torvalds
2012-10-03 23:12       ` Randy Dunlap
2012-10-09  4:31   ` Chris Zankel
2012-10-03 23:48 ` Al Viro
2012-10-04  0:07   ` Max Filippov
2012-10-04 18:45 ` Geert Uytterhoeven
2012-10-04 19:21   ` Chris Zankel

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=506CC33F.4090308@zankel.net \
    --to=chris@zankel.net \
    --cc=akpm@linux-foundation.org \
    --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