From: Stefan Jeglinski <jeglin@4pi.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: linuxppc_2_5 == 2.4.17?
Date: Thu, 27 Dec 2001 11:06:16 -0500 [thread overview]
Message-ID: <p04330100b850f62b47e1@[66.57.250.32]> (raw)
I may be missing the obvious, because it's been a looong time since I
played with a development version, but...
I rsynced the linuxppc_2_5 tree from mvista, and although the config
settings are obviously different and with new items, it is set to
build as 2.4.17 (as per the Makefile and version.h), just like
linuxppc_2_4. Shouldn't it instead be 2.5.1 or 2.5.2pre2 or something?
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-12-27 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-27 16:06 Stefan Jeglinski [this message]
2001-12-28 15:35 ` linuxppc_2_5 == 2.4.17? Tom Rini
[not found] ` <p04330100b85243b7a911@[66.57.250.32]>
[not found] ` <20011228155810.GN712@cpe-24-221-152-185.az.sprintbbd.net>
2001-12-28 18:28 ` Stefan Jeglinski
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='p04330100b850f62b47e1@[66.57.250.32]' \
--to=jeglin@4pi.com \
--cc=linuxppc-dev@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).