From: Paul Jackson <pj@sgi.com>
To: Evan Hisey <barnowl@unix.eng.ua.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Thu, 22 Jul 2004 15:57:59 -0700 [thread overview]
Message-ID: <20040722155759.0299dbc7.pj@sgi.com> (raw)
In-Reply-To: <40FFD760.8060504@unix.eng.ua.edu>
Evan,
Have you found (1) Linus' 2.6 bk tree to meet your needs over the last
few months? Or (2) has it been too unstable for you?
If (1), seems like you might be in good shape, as from what I can
gather of this (not being in Ottawa) next month looks alot like
last month, so far as how Linux is developed.
If (2), then perhaps there is an opportunity here for a derivative of
Linus' tree that is "stabilized a bit", but not overly patched like
certain vendor kernels I won't name.
Yes, we'd all like the head kernel to march to the beat of our
particular needs, rapidly changing and adding what we need without
delay, leaving the rest untouched, and never breaking.
Now ... back to reality ...
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-07-22 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:04 A users thoughts on the new dev. model Evan Hisey
2004-07-22 22:25 ` Bill Davidsen
2004-07-23 13:58 ` H. Peter Anvin
2004-07-23 15:24 ` szonyi calin
2004-07-23 16:39 ` David Ford
2004-07-23 19:06 ` Xiong Jiang
2004-07-23 20:00 ` Tim Wright
2004-07-23 21:40 ` Adrian Bunk
2004-07-23 23:04 ` hpa
2004-07-24 10:38 ` Adrian Bunk
2004-07-27 20:08 ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson [this message]
2004-07-27 20:20 ` Bill Davidsen
2004-07-28 7:31 ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei
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=20040722155759.0299dbc7.pj@sgi.com \
--to=pj@sgi.com \
--cc=barnowl@unix.eng.ua.edu \
--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.