linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
	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 23:00:07 +1100	[thread overview]
Message-ID: <20101220230007.e82487b8.sfr@canb.auug.org.au> (raw)
In-Reply-To: <AANLkTi=gjHyMt=W4-+PSMzt7PN7i-_Yvmx7EE8z0z74q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

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.

> 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. 

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2010-12-20 12:00 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 [this message]
2010-12-20 12:12   ` Sedat Dilek
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=20101220230007.e82487b8.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=ftpadmin@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.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).