[lkml]   [2010]   [Dec]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: Tree for December 27
On Mon, Dec 27, 2010 at 10:11 AM, Stephen Rothwell <> wrote:
> Hi,
> On Mon, 27 Dec 2010 09:04:06 +0100 Sedat Dilek <> wrote:
>> Can you try to upload/push via IPADDR?
> I can only upload to, the rest is done by the mirroring
> software.  I have no access to any of the other machines.

I was wondering about still "slow mirrors" as also checking out before
Xmas was very slow.
Now, seeing from an end-users point, the checking-out is just fine.
I tried to clone
"$GIT_MIRROR/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git" where

1. git://
2. git://
3. git//
4. git//

All checkouts had around 680-690KiB/s.


>> Can you please upload the patch-diff to
>> <>?
> If you mean for next-20101223, then there wasn't one.  I ran out of time
> and just threw away what I had done.
> If you mean generally, then (see above) it depends on the mirroring
> software.

Dunno what you mean with "mirroring software", but I am primarily
interested in the patch-v2.6.37-rc7-next-20101227 than in an updated
linux-next GIT repo.
IMHO, it should be possible to generate this patch from your local GIT
repo and upload the diff-patch to whereever is fast and accessible by
My kernel-build-system has as base a vanilla upstream (here:
2.6.37-rc7) against which I apply an individual patch-series incl. the
linux-next diff-patch.
Hope this helps a bit to understand what I was talking about.

- Sedat -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2010-12-27 10:57    [W:0.059 / U:2.272 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site