From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ftpadmin@kernel.org
Subject: Re: linux-next: Tree for December 20
Date: Mon, 20 Dec 2010 13:12:06 +0100 [thread overview]
Message-ID: <AANLkTin4dvM1B8GkxZH6DADJVg4ZWNSQvUHAviy-4O2J@mail.gmail.com> (raw)
In-Reply-To: <20101220230007.e82487b8.sfr@canb.auug.org.au>
On Mon, Dec 20, 2010 at 1:00 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi,
>
> On Mon, 20 Dec 2010 12:46:08 +0100 Sedat Dilek <sedat.dilek@googlemail.com> wrote:
>>
>> >
>> > [The mirroring on kernel.org is running slowly]
>>
>> Indeed, you know what's wrong with the mirrors?
>
> I don't know what is wrong. The mirroring just seems to be much slower
> in the last week or so. Today, it was just over three hours from when I
> uploaded linux-next until it was mirrored out.
>
> I have cc'd the admins.
>
Thanks.
>> Can you upload the diff-patch (patch-v2.6.37-rc6-next-20101220) to [1]
>> from your local-tree or place it somewhere else?
>
> I cannot upload directly to www.kernel.org, I up load to the same place
> on master.kernel.org and the mirroring system puts it on www.kernel.org.
>
I could download the diff-patch.
$ wget http://www.kernel.org/pub/linux/kernel/v2.6/next/patch-v2.6.37-rc6-next-20101220.bz2
- Sedat -
next prev parent reply other threads:[~2010-12-20 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 11:46 linux-next: Tree for December 20 Sedat Dilek
2010-12-20 12:00 ` Stephen Rothwell
2010-12-20 12:12 ` Sedat Dilek [this message]
2010-12-20 18:29 ` J.H.
2010-12-20 20:47 ` Stephen Rothwell
2010-12-20 18:34 ` Chris Ball
-- strict thread matches above, loose matches on Subject: below --
2010-12-20 9:00 Stephen Rothwell
2010-12-20 16:14 ` Zimny Lech
2010-12-20 20:49 ` 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=AANLkTin4dvM1B8GkxZH6DADJVg4ZWNSQvUHAviy-4O2J@mail.gmail.com \
--to=sedat.dilek@googlemail.com \
--cc=ftpadmin@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sedat.dilek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.