linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Christoph Hellwig <hch@infradead.org>,
	Andrew Morton <akpm@osdl.org>, Chris Wedgwood <cw@f00f.org>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm1
Date: Mon, 10 May 2004 23:37:20 -0700	[thread overview]
Message-ID: <20040511063720.GA1397@holomorphy.com> (raw)
In-Reply-To: <20040511072132.B12187@infradead.org>

On Mon, May 10, 2004 at 05:14:13PM -0700, Andrew Morton wrote:
>> If someone had done the kernel and userspace work 6-12 months ago then
>> sure, we wouldn't be in this situation.

On Tue, May 11, 2004 at 07:21:32AM +0100, Christoph Hellwig wrote:
> Well, the question is why did those folks who care about it (Oracle it
> seems) not do it 6-12 month ago?
> This oh shit oracle needs it we need to come up with a hack mentality
> sucks big time.  If oracle (or $ISV/$IHV) they should send patches in
> time so we can discuss it.  In fact these patches don't even come from
> Oracle but from Intel which shows something is seriously wrong with all
> this.

There were a combination of factors contributing to this, including
release-oriented efforts distracting ppl from 2.6 contributions,
disagreements outside kernel.org as to how to resolve this that
resulted in divergent solutions instead of any kind of agreement on a
solution, and so on.

IMHO the only opportunity for convergence etc. is this kind of flamewar
plus actual code rolling in atop it. I'm in the midst of some upheaval
(e.g. on the road plus having getting X running on laptop issues) so
please be patient while I get set up to write whatever code people want
to talk about for whatever alternative solutions they want implemented.

Thanks.


-- wli

  reply	other threads:[~2004-05-11  6:41 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10  9:45 2.6.6-mm1 Andrew Morton
2004-05-10 10:52 ` 2.6.6-mm1 Dominik Karall
2004-05-10 11:18   ` 2.6.6-mm1 Dave Jones
2004-05-10 12:20     ` 2.6.6-mm1 Nick Piggin
2004-05-10 12:22       ` 2.6.6-mm1 Dave Jones
2004-05-10 12:35 ` 2.6.6-mm1: FB_ASILIANT: no help text Adrian Bunk
2004-05-10 12:45 ` 2.6.6-mm1: a different CONFIG_STANDALONE approach Adrian Bunk
2004-05-10 12:57   ` Adrian Bunk
2004-05-10 20:00   ` Andrew Morton
2004-05-10 14:38 ` 2.6.6-mm1 Norberto Bensa
2004-05-10 14:55   ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:02     ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:22       ` 2.6.6-mm1 Dominik Karall
2004-05-10 15:33         ` 2.6.6-mm1 Norberto Bensa
2004-05-10 15:20 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  5:21   ` 2.6.6-mm1 Andrew Morton
2004-05-10 21:37 ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:02   ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:05     ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:15       ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:20         ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 22:47           ` 2.6.6-mm1 Andrew Morton
2004-05-10 22:48             ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:16         ` 2.6.6-mm1 Matt Mackall
2004-05-10 22:27     ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 22:48       ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:01         ` 2.6.6-mm1 Valdis.Kletnieks
2004-05-10 23:11     ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:14       ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:28       ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:33         ` 2.6.6-mm1 Chris Wedgwood
2004-05-10 23:51           ` 2.6.6-mm1 Andrew Morton
2004-05-10 23:53             ` 2.6.6-mm1 Chris Wedgwood
2004-05-11  0:14               ` 2.6.6-mm1 Andrew Morton
2004-05-11  0:24                 ` 2.6.6-mm1 Wim Coekaerts
2004-05-11  1:10                   ` 2.6.6-mm1 Andrew Morton
2004-05-11  1:51                     ` 2.6.6-mm1 Wim Coekaerts
2004-05-11  6:23                       ` 2.6.6-mm1 Christoph Hellwig
2004-05-12  2:44                         ` 2.6.6-mm1 Andrea Arcangeli
2004-05-12  5:11                           ` 2.6.6-mm1 Chris Wedgwood
2004-05-11 15:12                       ` 2.6.6-mm1 Wim Coekaerts
2004-05-12  5:42                         ` 2.6.6-mm1 Christoph Hellwig
2004-05-12  5:50                           ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:22                     ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:21                 ` 2.6.6-mm1 Christoph Hellwig
2004-05-11  6:37                   ` William Lee Irwin III [this message]
2004-05-11  6:18             ` 2.6.6-mm1 Christoph Hellwig
2004-05-10 23:33       ` 2.6.6-mm1 Chris Wright
2004-05-11  1:59         ` 2.6.6-mm1 Matt Mackall
2004-05-11 14:34   ` 2.6.6-mm1 Stephen Smalley
2004-05-11 16:48     ` 2.6.6-mm1 Chris Wright
2004-05-12 12:49 ` 2.6.6-mm1 Sean Neakums
2004-05-12 19:26   ` 2.6.6-mm1 Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2004-05-10 12:43 2.6.6-mm1 Sid Boyce
2004-05-12  8:13 ` 2.6.6-mm1 Andrew Morton
2004-05-10 16:50 2.6.6-mm1 Sid Boyce
     [not found] <fa.j4d62qo.1144tpk@ifi.uio.no>
     [not found] ` <fa.gg699ad.b2omr9@ifi.uio.no>
2004-05-11  6:33   ` 2.6.6-mm1 Andy Lutomirski
2004-05-11 10:34 2.6.6-mm1 Sid Boyce
2004-05-11 14:49 2.6.6-mm1 Neil Schemenauer
2004-05-11 18:55 ` 2.6.6-mm1 Andrew Morton
2004-05-12 12:26 2.6.6-mm1 Sid Boyce
2004-05-12 15:27 2.6.6-mm1 Sid Boyce

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=20040511063720.GA1397@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@osdl.org \
    --cc=cw@f00f.org \
    --cc=hch@infradead.org \
    --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 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).