[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPj87rOxZxJAB-2FqdBV9jHJ3gcbbSvfARhUtF39HfM_eDryQw@mail.gmail.com>
Date: Thu, 1 Dec 2016 20:50:01 +0000
From: Daniel Stone <daniel@...ishbar.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Stone <daniels@...labora.com>,
Rob Clark <robdclark@...il.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
DRI <dri-devel@...ts.freedesktop.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thierry Reding <thierry.reding@...il.com>
Subject: Re: linux-next: problems fetching the drm-intel, etc trees
Hi Stephen,
On 1 December 2016 at 20:45, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> On Thu, 01 Dec 2016 11:02:26 +0000 Daniel Stone <daniels@...labora.com> wrote:
>> Sorry about this, it is quite bad. I think having mirrors for the key DRM
>> trees on GitHub is a good idea though, and I can get to setting that up.
>> Stephen, you need DRM (airlied), drm-misc, drm-panel, drm-intel, drm-tegra,
>> drm-exynos and drm-msm, right?
>
> Well, here are the trees I fetch from *.freedesktop.org:
>
> [...]
>
> I did not have any trouble with the people.fd.o ones.
That's actually interesting, given that they lie on the same host.
Perhaps it means that the locally-mounted ones were fine, and it was
the NFS (cough) mount between git/anongit which took a dive ... thanks
for the datapoint!
Cheers,
Daniel
Powered by blists - more mailing lists