From: Jack Stone <jwjstone@fastmail.fm>
To: markh@compro.net
Cc: Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: git question
Date: Thu, 02 Feb 2012 19:49:38 +0000 [thread overview]
Message-ID: <4F2AE8D2.2090000@fastmail.fm> (raw)
In-Reply-To: <4F2AE6E9.5090402@compro.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 02/02/12 19:41, Mark Hounschell wrote:
> It's been a while but this used to work.
>
> # git clone
> git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-allstable.git
>
>
Cloning into linux-2.6-allstable...
> fatal: The remote end hung up unexpectedly
>
> Google showed nothing helpful? Where do I go. I need to bisect
> from 2.6.38 to 2.6.39
>
That repo has been deleted. The full list is available at:
git.kernel.org
If you want to bisect 2.6.38 -> 2.6.39 then I sugest you try :
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Which is Linus' official repo. If you want to bisect from 2.6.38.x ->
something else then you will have to try the stable repo, I think the
following will help:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
The only thing to be careful of is that 2.6.39.x is not a direct
decendant of 2.6.38.x, but it is a direct decentant of 2.6.38: the
stable trees have patches added in parallel.
Hope this helps,
Jack
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iJwEAQECAAYFAk8q6M4ACgkQNmg8QyarTdKLdQP/dyQ8TJVNTPwU5mcQiDP+GtIs
lhDlBCDqMRLgpIRz3Wrju/nJQQILv2lUbIGrCpXNT59F12UOTLbMDE6MDNXt8x+j
Vk8BKZhKcu4sNWXWvSVkqMLWBVhk1wPQkgw0mveaiGvf5DLV7WQunD9hwmSF05lf
gvJGkTTHew13IUv8j5E=
=B7MR
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-02-02 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 19:41 git question Mark Hounschell
2012-02-02 19:49 ` Jack Stone [this message]
2012-02-02 19:57 ` Mark Hounschell
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=4F2AE8D2.2090000@fastmail.fm \
--to=jwjstone@fastmail.fm \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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