From: "Dr. David Alan Gilbert" <gilbertd@treblig.org>
To: Dave Jones <davej@codemonkey.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: lkml, bugme.osdl.org?
Date: Wed, 4 Dec 2002 18:32:35 +0000 [thread overview]
Message-ID: <20021204183235.GA701@gallifrey> (raw)
In-Reply-To: <20021204124227.GB647@suse.de>
* Dave Jones (davej@codemonkey.org.uk) wrote in reply to my reply:
>
> This was something that was brought up in a discussion at the kernel
> summit by (I think) Paul Mackerras. The question was how to make
> sure we get all arch's in sync before doing a release.
> It should be fairly straightforward thing to do for 2.6.x releases,
> but during 2.5.x when stuff is changing so rapidly, it doesn't make
> sense to hold up the majority of users just so the other archs can
> play catch up.
True; thats why I only started submitting these now we are feature
chilled. I reckoned it was important not to get into the misconception
we didn't have many bugs left because things were starting to chug along
nicely on x86.
> > Don't forget that ia64, x86-64 and s390 are all potentially growing
> > users of Linux.
>
> ia64 and x86-64 maybe, but s390 is way out of the pricerange of most
> Linux users. Those who can afford it will likely use distro kernels anyway
> due to the added support they paid for.
True; but sometimes people have desires to run the same/similar kernel
versions on all their systems and/or use some patches without having to
have versions for all systems.
> > Linux on ARM, MIPS and PPC also has a healthy band of
> > productive (commercial and home) users.
>
> Russell has done a great job at keeping ARM up to date in 2.5,
> as have the PPC folks. For the most part, the archs aren't that
> out of sync. (Insert comedy remark here about m68k being more
> up to date than alpha).
Indeed - (Alpha is actually one of the few non-x86 architectures
that actually built fully for me in a recent 2.5.x - and made a passable
attempt at booting)
Dave
---------------- Have a happy GNU millennium! ----------------------
/ Dr. David Alan Gilbert | Running GNU/Linux on Alpha,68K| Happy \
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2002-12-04 18:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 7:24 lkml, bugme.osdl.org? Valdis.Kletnieks
2002-12-03 12:15 ` Dave Jones
2002-12-03 14:13 ` bill davidsen
2002-12-03 18:09 ` Tupshin Harper
2002-12-04 11:58 ` Dr. David Alan Gilbert
2002-12-04 12:35 ` Russell King
2002-12-04 12:42 ` Dave Jones
2002-12-04 18:32 ` Dr. David Alan Gilbert [this message]
2002-12-04 22:20 ` Russell King
2002-12-05 9:15 ` David Woodhouse
2002-12-05 9:25 ` William Lee Irwin III
2002-12-05 9:34 ` David Woodhouse
2002-12-05 9:35 ` William Lee Irwin III
2002-12-05 14:24 ` bill davidsen
2002-12-03 20:33 ` Martin J. Bligh
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=20021204183235.GA701@gallifrey \
--to=gilbertd@treblig.org \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.