From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: ok ... which source trees are the "right" choices?
Date: Tue, 29 Jun 2004 11:12:16 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406291107530.25353@localhost.localdomain> (raw)
based on wolfgang's recent reference to the linuxppc_2_4_devel
source tree at DENX, one has to ask -- how does one choose between the
various source trees to stay on top of things?
so far, i've established that, for the 2.6 kernel, i just keep
pulling the latest stuff from ppc.bkbits.net/linuxppc-2.5.
but what about the 2.4 kernel? besides the denx source (which,
based on experience, would be at the top of my list in terms of
choice), there's a whack of 2.4-based trees at ppc.bkbits.net.
and i've already confused myself this morning by looking at one
source tree while the discussion was referring to a different one.
dang.
so ... what's the recommendation? at the moment, it seems that i'd
want the denx 2.4 devel tree, and the bkbits 2.5 tree. thoughts?
rday
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-29 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 15:12 Robert P. J. Day [this message]
2004-06-29 17:56 ` Kgdb on Motorola 8451 ppc board Tameen Khan
2004-06-29 19:59 ` ok ... which source trees are the "right" choices? Tom Rini
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=Pine.LNX.4.60.0406291107530.25353@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).