From: David Edelsohn <dje@watson.ibm.com>
To: Kevin_Hendricks <khendricks@admin.ivey.uwo.ca>
Cc: hollis+@andrew.cmu.edu, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.13 build OOB?; need for some standardization here?
Date: Tue, 28 Sep 1999 14:39:11 -0400 [thread overview]
Message-ID: <9909281839.AA40920@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Kevin_Hendricks <khendricks@admin.ivey.uwo.ca> of "Tue, 28 Sep 1999 14:08:13 EDT." <199909281810.NAA06999@lists.linuxppc.org>
>>>>> Kevin Hendricks writes:
Kevin> I think we should either fix the way Linus and company decides when to release a
Kevin> stable version, or get our own "Alan Cox" to act as shepard over our own stable
Kevin> "ppc" kernel tree and make that person "official".
I tend to agree with Kevin here. The Linux core kernel developers
need to improve their release engineering process. I realize that
Linux/PPC was on the fringe for a long time, and both Paul and Cort have
done a lot of excellent work these past few months adding functionality
and improving the overall design. This rapid development makes it hard
for Linus and company to keep up. However, x86 development should not
break PowerPC and other ports as much as I have seen.
PowerPC and other architectures are becoming more important and
demonstrating the diversity of Linux. The breakage and instability does
not cast a good light on bazaar-style development model and Linux when we
are trying to broaden the Linux market.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-28 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-28 18:08 2.2.13 build OOB?; need for some standardization here? Kevin_Hendricks
1999-09-28 18:39 ` David Edelsohn [this message]
1999-09-30 18:04 ` Michel Lanners
[not found] <99092914301001.09002@argo.anu.edu.au>
1999-09-29 8:58 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
1999-09-28 15:20 Kevin_Hendricks
1999-09-28 16:15 ` Sriranga Veeraraghavan
1999-09-28 16:48 ` Geert Uytterhoeven
1999-09-28 17:27 ` Sriranga Veeraraghavan
1999-09-28 17:45 ` Hollis R Blanchard
1999-09-28 20:34 ` Deirdre Saoirse
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=9909281839.AA40920@marc.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=hollis+@andrew.cmu.edu \
--cc=khendricks@admin.ivey.uwo.ca \
--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).