From: "Markus F.X.J. Oberhumer" <markus@oberhumer.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] Update LZO compression code for v3.9
Date: Tue, 26 Feb 2013 21:02:02 +0100 [thread overview]
Message-ID: <512D14BA.5080401@oberhumer.com> (raw)
In-Reply-To: <CA+55aFy0jezoatAQKOYDPHifG9Lhyp2ZC=fYTFU2tpzxOhTa3Q@mail.gmail.com>
On 2013-02-26 18:28, Linus Torvalds wrote:
> On Thu, Feb 21, 2013 at 9:26 PM, Markus F.X.J. Oberhumer
> <markus@oberhumer.com> wrote:
>>
>> please pull my "lzo-update" branch from
>>
>> git://github.com/markus-oberhumer/linux.git lzo-update
>
> I *really* want github (and other general hosting) pull requests to be
> for signed tags, so that I can see your gpg key and there is some real
> trail of who things got pulled from.
>
> I prefer he signed tags even from trusted machines, because they allow
> for submitters to add comments directly for the merge, but for
> untrusted general hosting sites I will simply refuse to pull without
> them.
Ok, I have pushed a signed tag "lzo-update-signature-20130226", but
I'm not fully sure if that worked - at least
$ git verify-tag lzo-update-signature-20130226
gpg: Signature made Tue 26 Feb 2013 08:39:14 PM CET using DSA key ID 0B2043C9
gpg: Good signature from "Markus F.X.J. Oberhumer <markus@oberhumer.com>"
and the tag does show up at
https://github.com/markus-oberhumer/linux/commits/lzo-update-signature-20130226
My public key 0B2043C9 is available on many PGP key servers, e.g.
http://pgp.mit.edu:11371/pks/lookup?search=markus+oberhumer
Cheers,
Markus
>
> Linus
>
--
Markus Oberhumer, <markus@oberhumer.com>, http://www.oberhumer.com/
prev parent reply other threads:[~2013-02-26 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 5:26 [GIT PULL] Update LZO compression code for v3.9 Markus F.X.J. Oberhumer
2013-02-26 17:28 ` Linus Torvalds
2013-02-26 20:02 ` Markus F.X.J. Oberhumer [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=512D14BA.5080401@oberhumer.com \
--to=markus@oberhumer.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.