From: Jesper Nilsson <Jesper.Nilsson@axis.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: cris tree fetch failed
Date: Thu, 24 Jul 2008 16:06:18 +0200 [thread overview]
Message-ID: <20080724140618.GA27985@axis.com> (raw)
In-Reply-To: <20080724094800.5cb81577.sfr@canb.auug.org.au>
On Thu, Jul 24, 2008 at 01:48:00AM +0200, Stephen Rothwell wrote:
> Hi Jesper,
>
> Trying to fetch the cris tree today got this error:
>
> www.jni.nu[0: 83.254.46.216]: errno=Connection timed out
Yeah, my ISP decided to do some pretty intrusive service
(even pulling the power for the whole building) while
I was away in Ottawa.
It should be up by now.
> I will use yesterday's tree.
Thanks,
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
prev parent reply other threads:[~2008-07-24 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 23:48 linux-next: cris tree fetch failed Stephen Rothwell
2008-07-24 14:06 ` Jesper Nilsson [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=20080724140618.GA27985@axis.com \
--to=jesper.nilsson@axis.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).