From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Michal Simek <monstr@monstr.eu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error while fetching the microblaze tree
Date: Wed, 20 Sep 2017 09:26:00 +1000 [thread overview]
Message-ID: <20170920092600.716baffd@canb.auug.org.au> (raw)
In-Reply-To: <20160107093856.779af583@canb.auug.org.au>
Hi Michal,
On Thu, 7 Jan 2016 09:38:56 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Fetching the microblaze tree
> (git://git.monstr.eu/linux-2.6-microblaze.git#next) produces this error.
>
> fatal: read error: Connection reset by peer
>
> I will use the previously fetched version for today.
I have been unable to fetch the microblaze tree again for the past few
days. This time it is is getting:
git.monstr.eu[0: 195.88.143.27]: errno=Connection refused
--
Cheers,
Stephen Rothwell
next prev parent reply other threads:[~2017-09-19 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 22:38 linux-next: error while fetching the microblaze tree Stephen Rothwell
2016-01-07 7:10 ` Michal Simek
2016-01-07 8:13 ` Stephen Rothwell
2017-09-19 23:26 ` Stephen Rothwell [this message]
2017-09-20 5:36 ` Michal Simek
2017-09-20 13:09 ` Michal Simek
2017-09-20 22: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=20170920092600.716baffd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=monstr@monstr.eu \
/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