From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757094AbcK3XNF (ORCPT ); Wed, 30 Nov 2016 18:13:05 -0500 Received: from ozlabs.org ([103.22.144.67]:57615 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752856AbcK3XND (ORCPT ); Wed, 30 Nov 2016 18:13:03 -0500 Date: Thu, 1 Dec 2016 10:13:01 +1100 From: Stephen Rothwell To: Rob Clark Cc: Daniel Vetter , Intel Graphics , DRI , Thierry Reding , linux-next@vger.kernel.org, Linux Kernel Mailing List , Daniel Stone Subject: Re: linux-next: problems fetching the drm-intel, etc trees Message-ID: <20161201101301.48163c3b@canb.auug.org.au> In-Reply-To: References: <20161201093958.3be47944@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob, On Wed, 30 Nov 2016 17:49:24 -0500 Rob Clark wrote: > > yeah, {cgit,anongit}.fd.o have been having problems all day.. (the ssh > git urls for folks who have push access work fine).. although it has > worked for me a couple times today, given enough time. > > (not sure if we have github/etc mirrors somewhere? I do have a github > clone of mesa which is up to date as of ~10min ago.. I could do the > same for other git trees if someone somewhere is stuck) I have managed (with a lot of persistence) to fetch all the trees I need from there today. -- Cheers, Stephen Rothwell