From: Corey Minyard <cminyard@mvista.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error fetching the ipmi tree
Date: Tue, 21 Jul 2015 18:45:33 -0500 [thread overview]
Message-ID: <55AED99D.1060405@mvista.com> (raw)
In-Reply-To: <20150722082946.39366276@canb.auug.org.au>
On 07/21/2015 05:29 PM, Stephen Rothwell wrote:
> Hi Corey,
>
> 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?
-corey
next prev parent reply other threads:[~2015-07-21 23:45 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 [this message]
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
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=55AED99D.1060405@mvista.com \
--to=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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