From: Valdis.Kletnieks@vt•edu
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 Oct 5
Date: Wed, 05 Oct 2011 08:09:19 -0400 [thread overview]
Message-ID: <27222.1317816559@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 05 Oct 2011 19:37:50 +1100." <20111005193750.78af4ac777e9b69230d62375@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-10-05 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 8:37 linux-next: Tree for Oct 5 Stephen Rothwell
2011-10-05 12:09 ` Valdis.Kletnieks [this message]
2011-10-05 12:36 ` Stephen Rothwell
2011-10-05 13:17 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
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
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=27222.1317816559@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt$(echo .)edu \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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