From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@suse.de>, Jens Axboe <jens.axboe@oracle.com>,
Jan Engelhardt <jengelh@computergmbh.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.22
Date: Thu, 12 Jul 2007 17:20:23 -0700 [thread overview]
Message-ID: <20070712172023.d59c3001.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707121647420.20061@woody.linux-foundation.org>
On Thu, 12 Jul 2007 17:03:46 -0700 (PDT)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Thu, 12 Jul 2007, Greg KH wrote:
> >
> > Here are a bunch of USB patches and fixes against your 2.6.22 git tree.
>
> This also seems to contain some *totally*pointless* config variable
> changes, that actually break simple things like "make oldconfig".
>
> This commit is insane: acb11c8b8020f1f1b2545152020675ef32d09a58 "USB: fix
> gregkh-usb-usb-use-menuconfig-objects"
>
> It fixes nothing at all, quite the reverse. It makes the default be
> somethign that breaks everything, and more irritatingly, even if you
> answer 'y' (against the default), it breaks "make oldconfig", which will
> have ignored all the old options and now will ask you for all of them
> again.
>
> Yeah, that second part may be a "make oldconfig" bug, but regardless,
> these kinds of Kconfig changes are BAD, BAD, BAD!
>
> I hate how people do just stupid things to "clean up" config files
> (renaming config options etc), apparently never even bothering to think
> about whether a question is sane or not, or whether normal users want to
> see it or not.
>
> I know I'm not the only one who does "make oldconfig". Answering the same
> questions over and over again is not something *anybody* wants to do.
>
> So please stop this madness. I've reverted the change that left the
> menuconfig entry without a default, which at least fixes "make oldconfig",
> but I just found this really irritating. I can pretty much guarantee that
> nobody actually *tested* this change, did they?
>
I went through the same pain a few weeks ago and I _thought_ all except one
of these "fixes" got tossed. However it looks like the USB one escaped.
prev parent reply other threads:[~2007-07-13 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 23:42 Greg KH
2007-07-13 0:03 ` Linus Torvalds
2007-07-13 0:19 ` Greg KH
2007-07-13 0:20 ` Andrew Morton [this message]
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=20070712172023.d59c3001.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=jengelh@computergmbh.de \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®