linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: error while fetching the microblaze tree
@ 2016-01-06 22:38 Stephen Rothwell
  2016-01-07  7:10 ` Michal Simek
  2017-09-19 23:26 ` Stephen Rothwell
  0 siblings, 2 replies; 7+ messages in thread
From: Stephen Rothwell @ 2016-01-06 22:38 UTC (permalink / raw)
  To: Michal Simek; +Cc: linux-next, linux-kernel

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.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  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
  1 sibling, 1 reply; 7+ messages in thread
From: Michal Simek @ 2016-01-07  7:10 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel

[-- 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 --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  2016-01-07  7:10 ` Michal Simek
@ 2016-01-07  8:13   ` Stephen Rothwell
  0 siblings, 0 replies; 7+ messages in thread
From: Stephen Rothwell @ 2016-01-07  8:13 UTC (permalink / raw)
  To: Michal Simek; +Cc: linux-next, linux-kernel

Hi Michal,

On Thu, 7 Jan 2016 08:10:54 +0100 Michal Simek <monstr@monstr.eu> wrote:
>
> git server in under maintenance. Hopefully it will be solved soon.
> Sorry for trouble.

No trouble, just making sure it was not an oversight.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  2016-01-06 22:38 linux-next: error while fetching the microblaze tree Stephen Rothwell
  2016-01-07  7:10 ` Michal Simek
@ 2017-09-19 23:26 ` Stephen Rothwell
  2017-09-20  5:36   ` Michal Simek
  1 sibling, 1 reply; 7+ messages in thread
From: Stephen Rothwell @ 2017-09-19 23:26 UTC (permalink / raw)
  To: Michal Simek; +Cc: linux-next, linux-kernel

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  2017-09-19 23:26 ` Stephen Rothwell
@ 2017-09-20  5:36   ` Michal Simek
  2017-09-20 13:09     ` Michal Simek
  0 siblings, 1 reply; 7+ messages in thread
From: Michal Simek @ 2017-09-20  5:36 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]

Hi Stephen,

On 20.9.2017 01:26, Stephen Rothwell wrote:
> 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
> 

Thanks for letting me know. I have contacted admin to look at it.
Will let you know when it is recover.

Thanks,
Michal

-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  2017-09-20  5:36   ` Michal Simek
@ 2017-09-20 13:09     ` Michal Simek
  2017-09-20 22:27       ` Stephen Rothwell
  0 siblings, 1 reply; 7+ messages in thread
From: Michal Simek @ 2017-09-20 13:09 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel


[-- Attachment #1.1: Type: text/plain, Size: 1107 bytes --]

On 20.9.2017 07:36, Michal Simek wrote:
> Hi Stephen,
> 
> On 20.9.2017 01:26, Stephen Rothwell wrote:
>> 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
>>
> 
> Thanks for letting me know. I have contacted admin to look at it.
> Will let you know when it is recover.

Fixed now. Please try and let me know if there is any issue.

Thanks,
Michal


-- 
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs



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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: linux-next: error while fetching the microblaze tree
  2017-09-20 13:09     ` Michal Simek
@ 2017-09-20 22:27       ` Stephen Rothwell
  0 siblings, 0 replies; 7+ messages in thread
From: Stephen Rothwell @ 2017-09-20 22:27 UTC (permalink / raw)
  To: Michal Simek; +Cc: linux-next, linux-kernel

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

Hi Michal,

On Wed, 20 Sep 2017 15:09:30 +0200 Michal Simek <monstr@monstr.eu> wrote:
>
> Fixed now. Please try and let me know if there is any issue.

Looks good from here.  Thanks.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2017-09-20 22:27 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2017-09-20  5:36   ` Michal Simek
2017-09-20 13:09     ` Michal Simek
2017-09-20 22:27       ` Stephen Rothwell

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).