From: Wolfgang Denk <wd@denx.de>
To: Steven Hanley <sjh@wibble.net>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: what is the currently active devel tree?
Date: Wed, 03 Jan 2001 17:43:55 +0100 [thread overview]
Message-ID: <200101031643.f03GhtF03932@denx.local.net> (raw)
In-Reply-To: Your message of "Wed, 03 Jan 2001 20:48:25 +1100." <20010103204825.A16974@wibble.net>
In message <20010103204825.A16974@wibble.net> you wrote:
>
> remember which) about pre7 and such, so I am wondering is there a currently
> active tree somewhat in sync with kernel.org releases? or even with changes
> being made?
Good question.
> I suppose this could be the 2.5 bitkeeper tree being worked on? or some
> other bitkeeper tree?
OTOH: linuxppc_2_5 is still at -test13-pre3 while linuxppc_2_4 has
seen a lot of recent changes and is now at -prerelease-ac4
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Conscious is when you are aware of something, and conscience is when
you wish you weren't.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-03 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-03 9:48 what is the currently active devel tree? Steven Hanley
2001-01-03 16:43 ` Wolfgang Denk [this message]
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=200101031643.f03GhtF03932@denx.local.net \
--to=wd@denx.de \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.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;
as well as URLs for NNTP newsgroup(s).