From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: <linux-kernel@vger.kernel.org>, Mike Borrelli <mike@nerv-9.net>
Subject: Re: No love for the PPC
Date: Sat, 13 Oct 2001 07:46:15 +0200 [thread overview]
Message-ID: <20011013054615.1831@smtp.adsl.oleane.com> (raw)
In-Reply-To: <200110130452.f9D4qG9288830@saturn.cs.uml.edu>
In-Reply-To: <200110130452.f9D4qG9288830@saturn.cs.uml.edu>
>At the most recent Ottata Linux Symposium, there was a PowerPC
>session with about 20 people. Somebody did a poll, asking what
>people used. I was the only person who dared to use a kernel
>from Linus. Everone else was using the BenH and BitKeeper ones.
>
>This is a sorry state of affairs. If people are off using kernels
>from other places, there isn't a great incentive to keep the
>official Linus kernel updated. Nobody uses it anyway.
>
>Elimination of these non-Linus PowerPC trees would be great.
>(at least the "stable" ones should go, as they lure people
>away from the one true source tree)
That's not exactly how things happen.
Most users use the kernel that comes with their distro, which,
as usual in the linux world, is made of bits from here and there.
Some mac users use my kernels because they contain some bleeding
edge stuff that is not ready to be in a stable tree. It's an
experimental kernel and doesn't claim to be stable.
Now, PPC is a lot of very different machines, coordinating them
all is a complicated task, and having our own tree to handle the
merge work is pretty useful. This is the bk _2_4 "stable" tree, any
thing in there is supposed to be "pending" for Linus.
We would probably be happy to submit all what we have in _2_4_devel
once 2.5 is opened. It's our developemental tree. Occasionally,
parts of it are considered stable enough to get to _2_4, and
at that point, it might happen to take some time before beeing
fully merged in Linus tree, but we are doing our best.
Ben.
next prev parent reply other threads:[~2001-10-13 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 17:08 No love for the PPC Mike Borrelli
2001-10-12 17:30 ` Larry McVoy
2001-10-13 0:01 ` Aaron Lehmann
2001-10-13 0:53 ` Mike Fedyk
2001-10-12 17:56 ` Marc Wilson
2001-10-12 20:43 ` John Alvord
2001-10-13 4:52 ` Albert D. Cahalan
2001-10-13 5:46 ` Benjamin Herrenschmidt [this message]
2001-10-13 12:24 ` Olaf Hering
2001-10-13 18:47 ` Mike Fedyk
2001-10-13 20:44 ` Tom Rini
2001-10-15 5:57 ` Geert Uytterhoeven
2001-10-13 7:46 ` Paul Mackerras
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=20011013054615.1831@smtp.adsl.oleane.com \
--to=benh@kernel.crashing.org \
--cc=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@nerv-9.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