Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932510AbcKNP0Y (ORCPT ); Mon, 14 Nov 2016 10:26:24 -0500 Received: from ns1.pc-advies.be ([85.17.2.162]:53718 "EHLO spo001.leaseweb.nl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753178AbcKNP0U (ORCPT ); Mon, 14 Nov 2016 10:26:20 -0500 Date: Mon, 14 Nov 2016 16:26:16 +0100 From: Wim Van Sebroeck To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: linux-next: unable to fetch the watchdog tree Message-ID: <20161114152615.GA16294@spo001.leaseweb.nl> References: <20161114093426.2000ff4c@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161114093426.2000ff4c@canb.auug.org.au> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 315 Lines: 16 Hi Stephen, This has been fixed. Thanks for notifying me about it. Kind regards, Wim. > Hi Wim, > > For the past few days (nearly a week, sorry) fetching the watchdog tree > (git://www.linux-watchdog.org/linux-watchdog-next.git#master) has > resulted in a hung connection. > > -- > Cheers, > Stephen Rothwell