From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Valdis.Kletnieks@vt.edu
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 5
Date: Wed, 5 Oct 2011 23:36:25 +1100 [thread overview]
Message-ID: <20111005233625.a5a6e83e53a338c7b4e205ff@canb.auug.org.au> (raw)
In-Reply-To: <27222.1317816559@turing-police.cc.vt.edu>
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Hi,
On Wed, 05 Oct 2011 08:09:19 -0400 Valdis.Kletnieks@vt.edu wrote:
>
> On Wed, 05 Oct 2011 19:37:50 +1100, Stephen Rothwell said:
>
> > 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/ ).
>
> So I managed to bodger up my local linux-next tree, decided to start from
> scratch. Had a good 'git pull' of Linus's tree from yesterday, so I did a 'git
> clone -l' of that. Then:
>
> [/usr/src/linux-next] git remote add linux-next git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> [/usr/src/linux-next] git fetch linux-next
> fatal: The remote end hung up unexpectedly
>
> Am I pointing something in the wrong place, or does git need to be kicked at
> the kernel.org end? It's apparently tree-specific - pulling Linus's tree from
> git.kernel.org works just fine.
Yeah, linux-next is not back on git.kernel.org yet. See the note at the
top of the email you quoted above:
"The linux-next tree is now available from
git://github.com/sfrothwell/linux-next.git as a temporary measure while
the kernel.org servers are unavailable."
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-05 12:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 8:37 Stephen Rothwell
2011-10-05 12:09 ` Valdis.Kletnieks
2011-10-05 12:36 ` Stephen Rothwell [this message]
2011-10-05 13:17 ` Valdis.Kletnieks
2012-10-05 4:54 Stephen Rothwell
2016-10-05 5:14 Stephen Rothwell
2018-10-05 6:39 Stephen Rothwell
2018-10-05 13:48 ` Guenter Roeck
2021-10-05 8:06 Stephen Rothwell
2022-10-05 7:26 Stephen Rothwell
2023-10-05 3:45 Stephen Rothwell
2026-10-05 12:46 Mark Brown
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=20111005233625.a5a6e83e53a338c7b4e205ff@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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
all inboxes | Powered by JetHome®