From: Sebastian Reichel <sre@debian.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Carlos Chinea <carlos.chinea@nokia.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ext Linus Walleij <linus.walleij@linaro.org>,
"peter_henn@gmx.de" <peter_henn@gmx.de>,
"sjur.brandeland@stericsson.com" <sjur.brandeland@stericsson.com>,
"govindraj.ti@gmail.com" <govindraj.ti@gmail.com>,
"pawel.szyszuk@stericsson.com" <pawel.szyszuk@stericsson.com>
Subject: Re: HSI framework for linux-next
Date: Wed, 23 Nov 2011 18:26:50 +0100 [thread overview]
Message-ID: <20111123172650.GA1637@earth.universe> (raw)
In-Reply-To: <20111109085140.908f89d0e2b8160cc959d67c@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Wed, Nov 09, 2011 at 08:51:40AM +1100, Stephen Rothwell wrote:
> Hi Carlos,
>
> On Fri, 28 Oct 2011 12:27:46 +0300 Carlos Chinea <carlos.chinea@nokia.com> wrote:
> > ...
>
> Right, so -rc1 has been released so I can consider this. Just a couple of things:
>
> Linus (and the rest of us) is being a bit nmore paranoid about
> where to fetch trees from. Public git hosters (like gitorious) can be
> problematic since it is hard for us to verify the owners of trees
> reliably. You either need to apply for a kernel.org account, or you will
> need to add a signed tag to your tree before asking Linus to pull from
> it. And that atg will have to be singned with a GPG key that can be
> verified by Linus ...
>
> I am not sure how to translate that gitorious URI above into a
> simple, publically fetchable URI (git://gitorious.org...).
It has been two weeks. Did I miss any status updates?
Here's the git fetchable URI: git://gitorious.org/kernel-hsi/kernel-hsi.git
The existing tag is not signed though.
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-23 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 9:27 HSI framework for linux-next Carlos Chinea
2011-10-28 11:23 ` Artem Bityutskiy
2011-10-28 15:17 ` Shubhrajyoti
2011-10-28 18:45 ` Stephen Rothwell
2011-11-08 21:51 ` Stephen Rothwell
2011-11-23 17:26 ` Sebastian Reichel [this message]
2011-11-23 22:07 ` Stephen Rothwell
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=20111123172650.GA1637@earth.universe \
--to=sre@debian.org \
--cc=carlos.chinea@nokia.com \
--cc=govindraj.ti@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pawel.szyszuk@stericsson.com \
--cc=peter_henn@gmx.de \
--cc=sfr@canb.auug.org.au \
--cc=sjur.brandeland@stericsson.com \
/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