mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: What is standing in the way of opening the 2.5 tree?
Date: 27 Oct 2001 14:51:27 -0700	[thread overview]
Message-ID: <1004219488.11749.19.camel@stomata.megapathdsl.net> (raw)


Dear Linus,

It seems like there has been the expectation that the 2.5
tree was about to be opened for at least the last two months.
Would you be willing to state what the remaining impediments
are to opening the tree?  If you do so, it might help us 
more quickly resolve the remaining issues so we can begin
implementing the many changes we have anticipated working on
in the 2.5 tree.

That said, I'll note that gaining clear agreement or at least 
consensus in the design of the new 2.5 driver model may be a
prerequisite to opening the 2.5 tree.  I'm not sure whether
your intent is to wait for further design discussions to take 
place regarding other areas of major change.

Best wishes,

	Miles


             reply	other threads:[~2001-10-27 22:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-27 21:51 Miles Lane [this message]
2001-10-28  5:04 ` Jeff Garzik
2001-10-28 11:28   ` Allan Sandfeld
2001-10-28  5:46 ` David S. Miller
2001-10-29  1:58   ` Andreas Dilger
2001-10-30  5:09     ` What is standing in the way of opening the 2.5 tree? (quotas?) Neil Brown
2001-10-30 18:29     ` What is standing in the way of opening the 2.5 tree? Jan Kara
2001-10-30 23:03       ` Alan Cox
2001-10-31 13:19         ` Jan Kara
2001-10-30 21:11 Thomas Hood
2001-10-30 21:39 ` lost
2001-10-30 21:59   ` Sujal Shah
2001-10-31 19:18   ` Michael Peddemors
2001-10-31 19:39     ` David Lang
2001-10-30 22:44 ` Alan Cox
2001-10-31  1:36   ` Mike Fedyk

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=1004219488.11749.19.camel@stomata.megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®