From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for April 6
Date: Wed, 6 Apr 2011 14:19:48 +0200 [thread overview]
Message-ID: <BANLkTikG0=JbtbAQTOj9ij7EGPKb58sUbA@mail.gmail.com> (raw)
In-Reply-To: <20110406152915.bdc2ecd3.sfr@canb.auug.org.au>
On Wed, Apr 6, 2011 at 7:29 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> [The kernel.org mirroring is being slow.]
>
> Changes since 20110405:
>
> Dropped tree: xen
>
> The staging tree gained a conflict against the staging.current tree.
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).
Where is it?
No updates, only the US kernel-mirror in [3] has a patch.
In general:
Whom to contact in case of this GeoIP-related(?!) slowness to
kernel-mirrors for people from Europe?
This problem still exists here, since end of 2010 (so called
"android-stuff-sync").
"Here" means Wild Wild South-West Germany: *.kernel.org -> *.eu.k.o
I am now only taking the US-URLs to clone/pull/get my stuff.
Can you explain what's going on?
- Sedat -
[1] http://www.kernel.org/pub/linux/kernel/v2.6/next/?C=M;O=D
[2] http://git.eu.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=summary
[3] http://www.us.kernel.org/pub/linux/kernel/v2.6/next/patch-v2.6.39-rc1-next-20110406.gz
next prev parent reply other threads:[~2011-04-06 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 5:29 linux-next: Tree for April 6 Stephen Rothwell
2011-04-06 12:19 ` Sedat Dilek [this message]
2011-04-06 12:42 ` Stephen Rothwell
2011-04-06 12:59 ` Sedat Dilek
-- strict thread matches above, loose matches on Subject: below --
2009-04-06 6: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='BANLkTikG0=JbtbAQTOj9ij7EGPKb58sUbA@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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).