From: "Stephen Williams" <612dlag102@sneakemail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Relationship between bk libuxppc-2.4 and denx linuxppc_2_4_devel
Date: Thu, 10 Jun 2004 16:53:28 -0700 [thread overview]
Message-ID: <11675-28654@sneakemail.com> (raw)
This may have been asked on this list before, but I can't seem
to find it in the list archives.
What is the relationship between the linuxppc-2.4 tree from
bk, and the anonymous cvs linuxppc_2_4_devel hosted by Denx?
The latter *seems* more stable, but I'm hoping to integrate
in patches for me JSE board after cleaning up patches, and
it's not clear which tree I should work with.
--
Steve Williams "The woods are lovely, dark and deep.
steve at XXXXXXXXXX But I have promises to keep,
http://www.XXXXXXXXXX and lines to code before I sleep,
http://www.picturel.com And lines to code before I sleep."
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-06-10 23:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 23:53 Stephen Williams [this message]
2004-06-11 7:30 ` Relationship between bk libuxppc-2.4 and denx linuxppc_2_4_devel Wolfgang Denk
2004-06-11 20:59 ` Chris Clark
2004-06-11 21:44 ` Tom Rini
2004-06-11 21:58 ` Wolfgang Denk
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=11675-28654@sneakemail.com \
--to=612dlag102@sneakemail.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).