From: sebastian.hesselbarth@gmail.com (Sebastian Hesselbarth)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: Initial support for Marvell Berlin SoCs
Date: Wed, 18 Dec 2013 10:17:16 +0100 [thread overview]
Message-ID: <52B1681C.4040202@gmail.com> (raw)
In-Reply-To: <20131217154021.GM2609@titan.lakedaemon.net>
On 12/17/13 16:40, Jason Cooper wrote:
> Sebastian,
>
> On Mon, Dec 16, 2013 at 03:00:44PM +0100, Sebastian Hesselbarth wrote:
>> The following changes since commit 6ce4eac1f600b34f2f7f58f9cd8f0503d79e42ae:
>>
>> Linux 3.13-rc1 (2013-11-22 11:30:55 -0800)
>>
>> are available in the git repository at:
>> https://github.com/shesselba/linux-berlin.git topic/initial-for-v3.14
>
> It looks like you didn't use a signed tag here. I think we ran out of
> time at the mini-summit, so here's a quick howto:
Jason,
huge thanks for the summary! I'll keep it under my pillow :)
> $ git checkout topic/initial-for-v3.14
> $ git tag -s berlin-3.14 # assumes you have gpg key in local keyring
>
> # edit tag msg, enter pw for key
>
> $ git push --tags <remote> topic/initial-for-v3.14:topic/initial-for-v3.14
> $ git request-pull v3.13-rc1 <remote-pub> tags/berlin-3.14
>
> # check if it looks right, if so, pipe it to your email editor
>
> I know some are leary of github, and doing the signed tag gives us a
> provable method that what we are pulling is indeed what you created.
Hmm, yeah, I hear about it. I'll hopefully find a different git server
for the upcoming kernel versions.
> I'll send a signed email to Arnd, Olof, and Kevin with the fingerprint
> of the key you created at the ARM mini-summit.
Thanks again!
Sebastian
next prev parent reply other threads:[~2013-12-18 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 14:00 [GIT PULL] ARM: Initial support for Marvell Berlin SoCs Sebastian Hesselbarth
2013-12-17 15:40 ` Jason Cooper
2013-12-18 9:17 ` Sebastian Hesselbarth [this message]
2013-12-18 9:08 ` [GIT PULL v2] " Sebastian Hesselbarth
2013-12-19 18:25 ` Kevin Hilman
2013-12-22 20:10 ` Olof Johansson
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=52B1681C.4040202@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).