From: Corey Minyard <minyard@acm•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>,
Corey Minyard <cminyard@mvista•com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: error fetching the ipmi tree
Date: Sun, 19 Feb 2017 16:26:18 -0600 [thread overview]
Message-ID: <1d5ff522-7a88-ff61-bc0c-fff28d6882ae@acm.org> (raw)
In-Reply-To: <20170220080019.7972746b@canb.auug.org.au>
On 02/19/2017 03:00 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> On Wed, 22 Jul 2015 11:03:31 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>> On Tue, 21 Jul 2015 18:45:33 -0500 Corey Minyard <cminyard@mvista•com> wrote:
>>> On 07/21/2015 05:29 PM, Stephen Rothwell wrote:
>>>> While fetching the ipmi tree
>>>> (git://git.code.sf.net/p/openipmi/linux-ipmi#for-next), I get this
>>>> error:
>>>>
>>>> fatal: unable to connect to git.code.sf.net:
>>>> git.code.sf.net[0: 216.34.181.155]: errno=Connection refused
>>>>
>>>> I have been getting this for a few days now. The http and https URLs
>>>> don't work either (for me in Firefox).
>>> Looks like sourceforge had a serious outage on the 18th and are still
>>> working on restoring it. http://sourceforge.net/blog/category/sitestatus/
>>>
>>> Would you like me to move this someplace else?
>> Its not a real problem as long as you don't have any updates for the
>> tree before SF restore things.
> OK, it looks like SourceForge is out again:
>
> $ git fetch ipmi
> fatal: unable to connect to git.code.sf.net:
> git.code.sf.net[0: 216.34.181.155]: errno=Connection refused
>
> It might be worth considering moving to git.kernel.org if possible and
> not too much effort.
>
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.
I'm in the process of moving userland things I support to github, which
seems more
stable than SourceForge. Would that be better?
-corey
next prev parent reply other threads:[~2017-02-19 22:26 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 [this message]
2017-02-19 23:33 ` Stephen Rothwell
2017-03-09 21:41 ` Corey Minyard
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=1d5ff522-7a88-ff61-bc0c-fff28d6882ae@acm.org \
--to=minyard@acm$(echo .)org \
--cc=cminyard@mvista$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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