public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3
Date: 17 May 2002 16:14:45 -0700	[thread overview]
Message-ID: <1021677285.920.185.camel@sinai> (raw)
In-Reply-To: <86256BBC.007E84E7.00@smtpnotes.altec.com>

On Fri, 2002-05-17 at 15:59, Wayne.Brown@altec.com wrote:

> I have nothing against it being faster -- *as long as nothing about the way I
> use it changes.*  Most of my kernel upgrades are done while I'm at work,
> programming, doing Solaris system admin, sitting in meetings, making phone
> calls, or any of the other things my employer is paying me to do.  I have a cron
> job that checks kernel.org periodically and pops up a message on my screen when
> a new kernel patchset appears there.  When that happens, I quickly switch to
> another virtual console, ftp the patch, and then:

So we should curb progress in the name of you not spending 2 minutes
rewriting your bash scripts or repopulating your bash history with new
commands?

Bah go away.  I and most other people here are the exact opposite - give
us new features, less bugs, or innovation and we will surely change. 
Otherwise we would still be in the stone age.

	Robert Love


  reply	other threads:[~2002-05-17 23:14 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-17 22:59 kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3 Wayne.Brown
2002-05-17 23:14 ` Robert Love [this message]
2002-05-18  4:01 ` Horst von Brand
2002-05-18 12:57 ` Diego Calleja
  -- strict thread matches above, loose matches on Subject: below --
2002-05-19 10:26 Mike Galbraith
2002-05-18 10:25 Mike Galbraith
2002-05-18 17:32 ` Wayne.Brown
2002-05-18 18:11   ` Tomas Szepe
2002-05-18 21:15   ` DervishD
2002-05-20  4:31   ` Mike Fedyk
2002-05-20  5:09     ` Albert D. Cahalan
2002-05-20  5:18       ` Keith Owens
2002-05-20 14:29       ` Juan Quintela
2002-05-20  5:11     ` Keith Owens
2002-05-18  6:05 Wayne.Brown
2002-05-18 16:50 ` John Weber
2002-05-18  5:09 Wayne.Brown
2002-05-18  5:23 ` David Lang
2002-05-18 13:11 ` Diego Calleja
2002-05-17 20:53 Wayne.Brown
2002-05-17 21:14 ` Andrew Morton
2002-05-17 21:42   ` William Lee Irwin III
2002-05-17 22:16     ` Kai Germaschewski
2002-05-17 22:34       ` William Lee Irwin III
2002-05-17 22:40         ` Larry McVoy
2002-05-18  0:41       ` Oliver Xymoron
2002-05-17 22:09 ` Nicolas Pitre
2002-05-18  0:38 ` Oliver Xymoron
2002-05-17 19:51 Wayne.Brown
2002-05-17 20:09 ` Dave Jones
2002-05-17 20:25   ` Diego Calleja
2002-05-18 13:15 ` Paul P Komkoff Jr
2002-05-17 14:56 James Bottomley
2002-05-17 14:21 Wayne.Brown
2002-05-17 17:37 ` Adam Kropelin
2002-05-17 18:00   ` Robert Love
2002-05-16 22:42 Keith Owens
2002-05-17  0:10 ` Nicolas Pitre
2002-05-17  3:30   ` Tomas Szepe
2002-05-17  7:55     ` Russell King
2002-05-17  8:42     ` Miles Lane
2002-05-17 13:11       ` Dave Jones
2002-05-17 13:09     ` Denis Vlasenko
2002-05-17  8:17       ` Tomas Szepe
2002-05-17 13:39         ` Denis Vlasenko
2002-05-17  1:50 ` jeff millar
2002-05-17  2:04   ` Keith Owens
2002-05-17  2:26   ` Dave Jones
2002-05-17  7:11 ` Kenneth Johansson
2002-05-17 15:13   ` Nicolas Pitre
2002-05-17 15:19     ` Tomas Szepe
2002-05-17 15:42       ` Nicolas Pitre
2002-05-18  1:39         ` Keith Owens
2002-05-18  2:11           ` Nicolas Pitre
2002-05-18  2:19             ` Keith Owens
2002-05-17 18:19 ` Diego Calleja
2002-05-19 15:46 ` Pavel Machek

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=1021677285.920.185.camel@sinai \
    --to=rml@tech9.net \
    --cc=Wayne.Brown@altec.com \
    --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