mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: Rainer Ellinger <rainer@ellinger.de>
Cc: Steve Lord <lord@sgi.com>, Andreas Dilger <adilger@turbolabs.com>,
	"Dennis, Jim" <jdennis@snapserver.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Congrats Marcelo,
Date: Mon, 25 Feb 2002 01:38:39 +0100	[thread overview]
Message-ID: <E16f9A7-0002ry-00@starship.berlin> (raw)
In-Reply-To: <2D0AFEFEE711D611923E009027D39F2B153AD4@cdserv.meridian-data.com> <E16f8Ey-0002qn-00@starship.berlin> <3C7C18EB.4090509@ellinger.de>
In-Reply-To: <3C7C18EB.4090509@ellinger.de>

On February 27, 2002 12:23 am, Rainer Ellinger wrote:
> I think development in 2.5 should focus on including this waiting patches
> and come to a end and release asap. I think it's more important to catch up 
> with real world needs and existing patches, than working on new 
> developments.

They're both important.  If we focus only on features without evolving the 
underlying mechanisms we'll quickly end up with Windows.

Don't even think about asking Linus to stop working on new stuff.

-- 
Daniel

  reply	other threads:[~2002-02-26 23:47 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-26 20:38 Dennis, Jim
2002-02-26 20:50 ` H. Peter Anvin
2002-02-26 21:06 ` Andreas Dilger
2002-02-26 21:15   ` crypto (was Re: Congrats Marcelo,) Jeff Garzik
2002-02-26 22:33     ` Rik van Riel
2002-02-27 21:15       ` Michael H. Warfield
2002-02-27 21:57         ` Rik van Riel
2002-02-27 22:29           ` Michael H. Warfield
2002-02-27 23:06             ` Rik van Riel
2002-02-26 21:35   ` Robert Love
2002-02-26 21:40     ` arjan
2002-02-26 21:47       ` Robert Love
2002-02-24 23:51         ` Daniel Phillips
2002-02-28 22:32           ` Bill Davidsen
2002-03-01  9:50             ` Francois Romieu
2002-02-27  9:41     ` Francois Romieu
2002-02-26 21:56 ` Congrats Marcelo, Steve Lord
2002-02-24 23:39   ` Daniel Phillips
2002-02-26 23:23     ` Rainer Ellinger
2002-02-25  0:38       ` Daniel Phillips [this message]
2002-02-26 23:59     ` Martin J. Bligh
2002-02-27  0:47       ` Rainer Ellinger
2002-02-27  1:08         ` Matthew D. Pitts
2002-02-27  1:03       ` Martin J. Bligh
2002-02-26 22:59   ` Alan Cox
2002-02-26 22:59     ` Steve Lord
2002-02-25  0:28       ` Whither XFS? (was: Congrats Marcelo) Daniel Phillips
2002-02-26 23:39       ` Steve Lord
2002-02-25  8:22         ` Daniel Phillips
2002-02-26 23:00   ` Congrats Marcelo, J.A. Magallon
2002-02-26 23:07   ` Steve Lord
2002-02-25  0:10     ` Daniel Phillips
2002-02-28 21:52 ` Marcelo Tosatti
2002-03-01  0:01   ` Alan Cox
2002-03-01  0:37     ` Dave Jones
2002-03-01  1:13       ` Alan Cox
2002-03-01  1:03         ` Dave Jones
2002-03-01  1:51           ` Alan Cox
2002-03-01  1:28     ` Theodore Tso
2002-03-01  1:53       ` Mike Fedyk
2002-03-02 22:35         ` Hans-Peter Jansen
2002-03-02  3:43   ` Stephen Degler
2002-02-28 22:41 ` Bill Davidsen
2002-03-01  9:30 Andries.Brouwer
2002-03-01 18:33 ` Mike Fedyk
2002-03-02  4:13 Dennis, Jim
2002-03-02 18:24 ` David Ford
2002-03-03 22:58 ` Florian Weimer

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=E16f9A7-0002ry-00@starship.berlin \
    --to=phillips@bonn-fries.net \
    --cc=adilger@turbolabs.com \
    --cc=jdennis@snapserver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lord@sgi.com \
    --cc=rainer@ellinger.de \
    /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®