public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	linux-kernel@vger.kernel.org, mchehab@infradead.org
Subject: Re: default y idiocy
Date: Sat, 12 May 2007 22:09:54 +0200	[thread overview]
Message-ID: <20070512200954.GT4629@kernel.dk> (raw)
In-Reply-To: <20070512210944.52260991@the-village.bc.nu>

On Sat, May 12 2007, Alan Cox wrote:
> > Sorry, I don't buy that reason at all - it's a short term advantage,
> > causing long term pain. It's not what we have done in the past, don't
> > start doing crap like that now.
> 
> It doesn't really matter what it defaults too

It does matter what it defaults to, it should only default to y if it's
really needed. If it didn't matter, just default every driver to y?
Thanks, but no thanks.

> cp .config somewheresafe
> 
> Install new kernel
> 
> cp it back
> 
> make oldconfig

Ehm yes, kernel updating 101. What's your point? Do that with your
2.6.21 config and get met with lots of new questions on ps2, ethernet,
macintosh drivers, dab, etc. All because of some menuconfig shuffling.

-- 
Jens Axboe


  reply	other threads:[~2007-05-12 20:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12 18:23 default y idiocy Jens Axboe
2007-05-12 19:22 ` Jan Engelhardt
2007-05-12 19:27   ` Jens Axboe
2007-05-12 19:37     ` Jan Engelhardt
2007-05-12 19:45       ` Jens Axboe
2007-05-12 20:14         ` Jan Engelhardt
2007-05-13  0:46           ` Mauro Carvalho Chehab
2007-05-12 20:09     ` Alan Cox
2007-05-12 20:09       ` Jens Axboe [this message]
2007-05-12 19:58 ` Simon Arlott
2007-05-12 20:05   ` Jens Axboe
2007-05-12 20:56   ` James Bottomley
2007-05-13 16:46     ` Krzysztof Halasa
2007-05-12 21:14   ` Satyam Sharma

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=20070512200954.GT4629@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@infradead.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