From: Corey Minyard <tcminyard@gmail•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Corey Minyard <minyard@acm•org>
Cc: Corey Minyard <cminyard@mvista•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: error fetching the ipmi tree
Date: Thu, 9 Mar 2017 15:41:47 -0600 [thread overview]
Message-ID: <26148384-6fcb-0805-4d40-cce050ce8914@gmail.com> (raw)
In-Reply-To: <20170220103301.24f1ac6c@canb.auug.org.au>
On 02/19/2017 05:33 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> On Sun, 19 Feb 2017 16:26:18 -0600 Corey Minyard <minyard@acm•org> wrote:
>> Dang, I was hoping SourceForge had cleaned up their act. I can ask for
>> an account on
>> kernel.org, but I'm not sure I will be able to get one.
> Yeah, you need a well signed GPG key ...
>
>> I'm in the process of moving userland things I support to github, which
>> seems more
>> stable than SourceForge. Would that be better?
> Probably better than SourceForge :-) Keep in mind that Linus requires
> signed tags for pulls from basically anywhere besides kernel.org.
>
Ok, I've moved over to:
https://github.com/cminyard/linux-ipmi.git for-next
for now. I have created a new GPG key, when I get a chance to get
signatures
(probably not until Plumbers) I will attempt to move over to kernel.org.
Thank you,
-corey
next prev parent reply other threads:[~2017-03-09 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 22:29 linux-next: error fetching the ipmi tree Stephen Rothwell
2015-07-21 23:45 ` Corey Minyard
2015-07-22 1:03 ` Stephen Rothwell
2017-02-19 21:00 ` Stephen Rothwell
2017-02-19 22:26 ` Corey Minyard
2017-02-19 23:33 ` Stephen Rothwell
2017-03-09 21:41 ` Corey Minyard [this message]
2017-03-09 23:48 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2015-02-22 23:23 Stephen Rothwell
2015-02-23 2:12 ` Corey Minyard
2015-02-23 20:20 ` Stephen Rothwell
2015-02-23 21:44 ` Corey Minyard
2015-02-23 22:54 ` Stephen Rothwell
2015-02-24 0:06 ` Corey Minyard
2015-02-24 0:27 ` 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=26148384-6fcb-0805-4d40-cce050ce8914@gmail.com \
--to=tcminyard@gmail$(echo .)com \
--cc=cminyard@mvista$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=minyard@acm$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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