public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <monstr@monstr.eu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: error while fetching the microblaze tree
Date: Thu, 7 Jan 2016 08:10:54 +0100	[thread overview]
Message-ID: <568E0F7E.8080208@monstr.eu> (raw)
In-Reply-To: <20160107093856.779af583@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

Hi,

On 6.1.2016 23:38, Stephen Rothwell wrote:
> Hi Michal,
> 
> 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.

git server in under maintenance. Hopefully it will be solved soon.
Sorry for trouble.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Microblaze cpu - http://www.monstr.eu/fdt/
Maintainer of Linux kernel - Xilinx Zynq ARM architecture
Microblaze U-BOOT custodian and responsible for u-boot arm zynq platform



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-01-07  7:11 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 [this message]
2016-01-07  8:13   ` Stephen Rothwell
2017-09-19 23:26 ` Stephen Rothwell
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=568E0F7E.8080208@monstr.eu \
    --to=monstr@monstr.eu \
    --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