From: Daniel Stone <daniel@fooishbar.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Stone <daniels@collabora.com>,
Rob Clark <robdclark@gmail.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
DRI <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: linux-next: problems fetching the drm-intel, etc trees
Date: Thu, 1 Dec 2016 20:50:01 +0000 [thread overview]
Message-ID: <CAPj87rOxZxJAB-2FqdBV9jHJ3gcbbSvfARhUtF39HfM_eDryQw@mail.gmail.com> (raw)
In-Reply-To: <20161202074515.6ae9fa4c@canb.auug.org.au>
Hi Stephen,
On 1 December 2016 at 20:45, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> On Thu, 01 Dec 2016 11:02:26 +0000 Daniel Stone <daniels@collabora.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
prev parent reply other threads:[~2016-12-01 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 22:39 linux-next: problems fetching the drm-intel, etc trees Stephen Rothwell
2016-11-30 22:49 ` Rob Clark
2016-11-30 23:13 ` Stephen Rothwell
2016-12-01 11:02 ` Daniel Stone
2016-12-01 20:45 ` Stephen Rothwell
2016-12-01 20:50 ` Daniel Stone [this message]
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=CAPj87rOxZxJAB-2FqdBV9jHJ3gcbbSvfARhUtF39HfM_eDryQw@mail.gmail.com \
--to=daniel@fooishbar.org \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).