From: Rob Landley <rob@landley.net>
To: Nicolas Pitre <nico@cam.org>, John Bradford <john@grabjohn.com>
Cc: lkml <linux-kernel@vger.kernel.org>, <szepe@pinerecords.com>
Subject: Re: Messing with Kconfig.
Date: Fri, 1 Aug 2003 13:12:19 -0400 [thread overview]
Message-ID: <200308011312.19045.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0308011112310.9934-100000@xanadu.home>
On Friday 01 August 2003 11:27, Nicolas Pitre wrote:
> On Fri, 1 Aug 2003, John Bradford wrote:
> > > So I'm looking at menuconfig and contemplating rearranging the heck out
> > > of it
> >
> > Please don't. This comes up from time to time on the mailing list,
> > and massive re-arrangements are usually a Bad Thing.
>
> Of course "massive" re-arrangements all at once have always been rejected,
> and we've seen obvious examples of that in the kernel build/config system
> area already.
>
> One should have learned, though, that small incremental changes can achieve
> similar results and are much more acceptable to the rest of the community.
And one has to go especially slow during -test. And if a change doesn't get
merged immediately, you have to maintain it until there's an opening. And if
somebody ever actually tells you WHY it's wrong, this is not criticism but an
opportunity to FIX it (sometimes by dropping the change)...
> Nicolas
Rob
next prev parent reply other threads:[~2003-08-01 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 9:01 Messing with Kconfig John Bradford
2003-08-01 9:12 ` Rob Landley
2003-08-01 15:27 ` Nicolas Pitre
2003-08-01 17:12 ` Rob Landley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-01 8:37 Rob Landley
2003-08-01 9:33 ` Roman Zippel
2003-08-01 13:35 ` Bartlomiej Zolnierkiewicz
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=200308011312.19045.rob@landley.net \
--to=rob@landley.net \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=szepe@pinerecords.com \
/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).