From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 17 May 2002 19:14:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 17 May 2002 19:14:47 -0400 Received: from gateway-1237.mvista.com ([12.44.186.158]:37873 "EHLO hermes.mvista.com") by vger.kernel.org with ESMTP id ; Fri, 17 May 2002 19:14:47 -0400 Subject: Re: kbuild 2.5 is ready for inclusion in the 2.5 kernel - take 3 From: Robert Love To: Wayne.Brown@altec.com Cc: linux-kernel@vger.kernel.org In-Reply-To: <86256BBC.007E84E7.00@smtpnotes.altec.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 17 May 2002 16:14:45 -0700 Message-Id: <1021677285.920.185.camel@sinai> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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