From: Sam Ravnborg <sam@ravnborg.org>
To: John Kacur <jkacur@gmail.com>
Cc: linux-kbuild@vger.kernel.org, lkml@vger.kernel.org
Subject: Re: [PATCH] Change Kbuild message to match default
Date: Wed, 30 Jul 2008 22:26:55 +0200 [thread overview]
Message-ID: <20080730202655.GA12148@uranus.ravnborg.org> (raw)
In-Reply-To: <520f0cf10807260234v64297490l6db807fee0864cc5@mail.gmail.com>
On Sat, Jul 26, 2008 at 11:34:14AM +0200, John Kacur wrote:
> On Wed, Jul 16, 2008 at 12:31 AM, jkacur <jkacur@gmail.com> wrote:
> > Change the Kbuild "If unsure" message to match the default.
> >
> > Signed-off-by: John Kacur <jkacur at gmail dot com>
> >
> > Index: linux-2.6.26/init/Kconfig
> > ===================================================================
> > --- linux-2.6.26.orig/init/Kconfig
> > +++ linux-2.6.26/init/Kconfig
> > @@ -522,7 +522,7 @@ config CC_OPTIMIZE_FOR_SIZE
> > Enabling this option will pass "-Os" instead of "-O2" to gcc
> > resulting in a smaller kernel.
> >
> > - If unsure, say N.
> > + If unsure, say Y.
> >
> > config SYSCTL
> > bool
> >
>
> This seems like a no-brainer to me that the default and the "If
> unsure" message should match, any reason you haven't picked-it up?
Two reasons:
1) I have not started to look at new patches until now
And this is due to several reasons.
First off I have been without internet for a while.
And secondly I do try to avoid new patches during the
merge window which does not fix merge issues.
2) I am not convinced that "default y" is really what we want.
What does popular distroes use (aka what gets wide testing?).
Sam
next prev parent reply other threads:[~2008-07-30 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 22:31 [PATCH] Change Kbuild message to match default jkacur
2008-07-26 9:34 ` John Kacur
2008-07-30 20:26 ` Sam Ravnborg [this message]
2008-07-30 23:23 ` John Kacur
2008-07-31 21:34 ` Sam Ravnborg
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=20080730202655.GA12148@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jkacur@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=lkml@vger.kernel.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