From: Jens Axboe <axboe@kernel.dk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: sedat.dilek@gmail.com, Sedat Dilek <sedat.dilek@googlemail.com>,
linux-next@vger.kernel.org
Subject: Re: linux-next: failed to fetch block tree
Date: Mon, 11 Apr 2011 11:14:32 +0200 [thread overview]
Message-ID: <4DA2C678.1050208@kernel.dk> (raw)
In-Reply-To: <20110407104040.daf2a613.sfr@canb.auug.org.au>
On 2011-04-07 02:40, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Thu, 7 Apr 2011 02:37:10 +0200 Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>>
>> On Thu, Apr 7, 2011 at 2:26 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>>
>>> Trying to fetch the block tree yesterday and today produced this error:
>>>
>>> git.kernel.dk[0: 95.166.99.235]: errno=Connection timed out
>>>
>>> I am using the block tree from next-20110405.
>>
>> Clone-able here:
>> git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-2.6-block.git
>
> Yes, but that is not the tree Jens has asked me to fetch.
My DSL went down while I was away. In general, the kernel.org repo
should be identical to the kernel.dk one. It's pushed out when changes
happen. It may lag due to the kernel.org mirror latencies, but apart
from that it should be fine.
So at least in the future, using the above kernel.org url is fine as a
backup.
--
Jens Axboe
next prev parent reply other threads:[~2011-04-11 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 0:26 linux-next: failed to fetch block tree Stephen Rothwell
2011-04-07 0:37 ` Sedat Dilek
2011-04-07 0:40 ` Stephen Rothwell
2011-04-11 9:14 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 1:45 Stephen Rothwell
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=4DA2C678.1050208@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--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).