linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: unable to fetch the mips tree
Date: Fri, 10 Sep 2010 02:49:54 +0200	[thread overview]
Message-ID: <20100910004954.GA8325@linux-mips.org> (raw)
In-Reply-To: <20100910102614.61909592.sfr@canb.auug.org.au>

On Fri, Sep 10, 2010 at 10:26:14AM +1000, Stephen Rothwell wrote:

> For the last couple of days, I have been getting the following error when
> trying to fetch mips tree:
> 
> git.linux-mips.org[0: 78.24.191.183]: errno=Connection refused

About 30h, I guess.  That's when the machine was upgraded and rebooted.
Fixed now.  Thanks for leting me know.

  Ralf

  reply	other threads:[~2010-09-10  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10  0:26 linux-next: unable to fetch the mips tree Stephen Rothwell
2010-09-10  0:49 ` Ralf Baechle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-10 21:20 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=20100910004954.GA8325@linux-mips.org \
    --to=ralf@linux-mips.org \
    --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;
as well as URLs for NNTP newsgroup(s).