From: Zimny Lech <napohybelskurwysynom2010@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 20
Date: Mon, 20 Dec 2010 17:14:34 +0100 [thread overview]
Message-ID: <AANLkTikerjf=yEyeq8cy-_yPRLcfx01=1M9x9sYJ2kEv@mail.gmail.com> (raw)
In-Reply-To: <20101220200013.df8fbc88.sfr@canb.auug.org.au>
Ave,
2010/12/20 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi all,
>
> [The mirroring on kernel.org is running slowly]
>
Looks like something is borked
Fetching linux-next
fatal: The remote end hung up unexpectedly
fatal: protocol error: bad pack header
error: Could not fetch linux-next
--
Slawa!
Zimny "Spie dziadu!" Lech z Wawelu
Hej, tam!
Wydarłem klejnot szans
http://www.youtube.com/watch?v=VXWTlYzVFUA
next prev parent reply other threads:[~2010-12-20 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 9:00 linux-next: Tree for December 20 Stephen Rothwell
2010-12-20 16:14 ` Zimny Lech [this message]
2010-12-20 20:49 ` Stephen Rothwell
2010-12-20 16:53 ` linux-next: Tree for December 20 (acpi_video) Randy Dunlap
2011-01-26 11:42 ` Ingo Molnar
2011-02-01 12:03 ` [upstream build breakage] " Ingo Molnar
2011-02-01 19:17 ` [PATCH] gpu/stub: fix acpi_video build error, fix stub kconfig dependencies Randy Dunlap
2011-02-02 1:35 ` Ingo Molnar
2011-02-28 17:03 ` [PATCH upstream build breakage] acpi: several drivers depend on NET Randy Dunlap
2011-02-28 20:37 ` Rafael J. Wysocki
2011-02-28 22:42 ` Rafael J. Wysocki
2011-03-01 0:00 ` Randy Dunlap
2011-03-01 0:12 ` Rafael J. Wysocki
2011-03-01 6:17 ` [build fix] ACPI: Fix build for CONFIG_NET unset Ingo Molnar
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
2010-12-20 18:29 ` J.H.
2010-12-20 20:47 ` Stephen Rothwell
2010-12-20 18:34 ` Chris Ball
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='AANLkTikerjf=yEyeq8cy-_yPRLcfx01=1M9x9sYJ2kEv@mail.gmail.com' \
--to=napohybelskurwysynom2010@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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.