linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	kbuild-devel <kbuild-devel@lists.sourceforge.net>
Subject: Re: linux kernel conf 0.8
Date: Thu, 10 Oct 2002 13:32:11 -0400	[thread overview]
Message-ID: <3DA5B99B.5080707@pobox.com> (raw)
In-Reply-To: 20021010192924.A13618@mars.ravnborg.org

Sam Ravnborg wrote:
> [cc: trimmed]
> 
> On Thu, Oct 10, 2002 at 10:18:06AM -0400, Jeff Garzik wrote:
> 
>>Personally I don't care about Config dependency checking...  they are 
>>not modified often enough to affect me, and even if they did, dependency 
>>checking based on changes to Config files can get ugly, AFAICS.  I just 
>>do a "bk -r co -Sq" and am done with it...
> 
> I care a lot about Config dependency checking, and you are not within the 
> group of people that I care about in this respect.
> 
> kernel-hackers has no problem realising that a "make oldconfig" is needed.
> 
> But I care about NN that follows 2.6 development, and update his/her
> tree each time a new version is posted at kernel.org.
> This group of people needs dependency checking on Config files -
> as can be seen by the number of reports that boils down to
> "run make oldconfig".


The kernel is written for people with a clue.  For people without a 
clue, they should use a vendor kernel or ESR's Aunt-Tillie-friendly system.

Dumbing-down the kernel is never the right answer.

	Jeff




  reply	other threads:[~2002-10-10 17:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0210081830350.4396-100000@home.transmeta.com>
2002-10-09 12:01 ` linux kernel conf 0.8 Roman Zippel
2002-10-09 13:35   ` Jeff Garzik
2002-10-09 13:55     ` Roman Zippel
2002-10-09 14:07       ` Jeff Garzik
2002-10-09 14:14       ` [kbuild-devel] " Brendan J Simon
2002-10-09 14:28         ` Jeff Garzik
2002-10-09 14:24   ` Brendan J Simon
2002-10-09 14:34     ` Randy.Dunlap
2002-10-09 14:45       ` J.A. Magallon
2002-10-09 15:14         ` Roman Zippel
2002-10-09 15:16       ` Linus Torvalds
2002-10-09 15:19         ` Randy.Dunlap
2002-10-09 16:29           ` Roman Zippel
2002-10-09 16:40             ` Christoph Hellwig
2002-10-09 18:39               ` Roman Zippel
2002-10-09 18:52                 ` Peter Samuelson
2002-10-09 19:28                   ` Randy.Dunlap
2002-10-09 19:39                     ` Sam Ravnborg
2002-10-09 19:47                       ` Randy.Dunlap
2002-10-09 14:55     ` [kbuild-devel] " Roman Zippel
2002-10-09 17:16   ` Sam Ravnborg
2002-10-09 17:37     ` Linus Torvalds
2002-10-09 17:55       ` Sam Ravnborg
2002-10-09 18:47         ` Linus Torvalds
2002-10-09 19:26           ` Sam Ravnborg
2002-10-09 20:41             ` Jeff Garzik
2002-10-09 22:49               ` Roman Zippel
2002-10-10 14:18                 ` Jeff Garzik
2002-10-10 17:29                   ` Sam Ravnborg
2002-10-10 17:32                     ` Jeff Garzik [this message]
2002-10-10 17:51                       ` Sam Ravnborg
2002-10-09 23:49         ` [kbuild-devel] " Brendan J Simon
2002-10-09 18:35       ` Jeff Garzik
2002-10-09  0:40 Roman Zippel

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=3DA5B99B.5080707@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=kbuild-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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).