From: Tom Rini <trini@kernel.crashing.org>
To: rdiz@alumni.deec.uc.pt
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Compiling kernel 2.6.7-rc1 for 8xx
Date: Thu, 27 May 2004 13:55:29 -0700 [thread overview]
Message-ID: <20040527205529.GL6763@smtp.west.cox.net> (raw)
In-Reply-To: <4786.62.48.238.11.1085678078.squirrel@alumni.deec.uc.pt>
On Thu, May 27, 2004 at 06:14:38PM +0100, rdiz@alumni.deec.uc.pt wrote:
>
> I don't know what kind of search I did before, but I found now some recent
> relevant posts about it. Thanks.
>
> BTW, do I have to use BitKeeper to download the 2.5 kernel tree?
No. For Linus' tree there are snapshots of the bitkeeper version on
kernel.org I believe, and for the linuxppc trees there are still rsync
mirrors on source.mvista.com.
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-27 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 17:14 Compiling kernel 2.6.7-rc1 for 8xx rdiz
2004-05-27 20:55 ` Tom Rini [this message]
2004-05-28 11:34 ` rdiz
-- strict thread matches above, loose matches on Subject: below --
2004-05-27 15:19 rdiz
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=20040527205529.GL6763@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rdiz@alumni.deec.uc.pt \
/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;
as well as URLs for NNTP newsgroup(s).