From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Re: RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default
Date: Thu, 24 Jan 2013 14:05:35 -0500 [thread overview]
Message-ID: <CAGfcS_=HFVMUBsWnJ-Zua9HxTAXqJ1=C8d3qWL6k=z-pAfhYmw@mail.gmail.com> (raw)
In-Reply-To: <5101844B.8070005@gentoo.org>
On Thu, Jan 24, 2013 at 1:58 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
> How about, you know what you're doing and are going to build a new
> kernel as soon as the emerge finishes (since the emerge is also
> bringing in a new gentoo-sources)??
Or my earlier example - USB_SUSPEND and such. If there end up being
lots of config checks that are fatal then users will inevitably end up
overriding them, and then they'll get burned when the check really
matters.
I think the better option in any case is to use a news item when
things change so that users can actually plan for the upcoming changes
and not find out in the middle of a build. News can be targeted at
those who need to know, it shows up for users 5 years from now if
still relevant not if otherwise, and it only shows up once when it
matters.
Rich
next prev parent reply other threads:[~2013-01-24 19:05 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 3:38 [gentoo-dev] RFC: CONFIG_CHECK_FATAL, making CONFIG_CHECKS fatal by default Robin H. Johnson
2013-01-22 3:45 ` Mike Gilbert
2013-01-22 3:56 ` Zac Medico
2013-01-22 4:10 ` Rick "Zero_Chaos" Farina
2013-01-22 4:14 ` Zac Medico
2013-01-22 9:22 ` Markos Chandras
2013-01-22 14:49 ` Zac Medico
2013-01-22 4:23 ` Mike Gilbert
2013-01-22 6:22 ` Sergey Popov
2013-01-22 6:44 ` [gentoo-dev] " Duncan
2013-01-22 14:51 ` [gentoo-dev] " Zac Medico
2013-01-22 18:40 ` Robin H. Johnson
2013-01-23 12:32 ` Fabio Erculiani
2013-01-23 12:50 ` Rich Freeman
2013-01-23 21:27 ` Fabio Erculiani
2013-01-23 23:17 ` Francesco Riosa
2013-01-24 1:10 ` Robin H. Johnson
2013-01-24 19:46 ` Fabio Erculiani
2013-01-22 11:11 ` vivo75
2013-01-22 11:56 ` Rich Freeman
2013-01-24 17:04 ` Dustin C. Hatch
2013-01-24 17:49 ` [gentoo-dev] " Duncan
2013-01-24 18:09 ` Rich Freeman
2013-01-24 18:18 ` Ian Stakenvicius
2013-01-24 18:24 ` Dustin C. Hatch
2013-01-24 18:25 ` Rich Freeman
2013-01-24 18:55 ` Michael Orlitzky
2013-01-24 18:58 ` Ian Stakenvicius
2013-01-24 19:05 ` Rich Freeman [this message]
2013-01-24 19:21 ` Michael Orlitzky
2013-01-24 20:26 ` vivo75
2013-01-24 20:39 ` Michael Orlitzky
2013-01-24 20:45 ` Michael Orlitzky
2013-01-25 0:29 ` vivo75
2013-01-25 0:37 ` Michael Orlitzky
2013-01-24 21:30 ` Rich Freeman
2013-01-26 10:34 ` Fabio Erculiani
2013-01-26 22:25 ` Duncan
2013-01-26 22:30 ` Fabio Erculiani
2013-01-26 22:54 ` Rich Freeman
2013-01-27 0:31 ` Peter Stuge
2013-01-27 1:06 ` Rich Freeman
2013-01-25 1:39 ` Duncan
2013-01-25 1:53 ` Robin H. Johnson
2013-01-25 2:22 ` Michael Orlitzky
2013-01-25 3:12 ` Rich Freeman
2013-01-25 3:27 ` Michael Orlitzky
2013-01-25 6:15 ` Duncan
2013-01-25 18:24 ` Nuno J. Silva
2013-01-25 18:47 ` Rich Freeman
2013-01-25 19:19 ` Christopher Head
2013-01-25 19:26 ` Rich Freeman
2013-01-25 19:47 ` Nuno J. Silva
2013-01-25 19:57 ` Rich Freeman
2013-01-25 20:06 ` Nuno J. Silva
2013-01-25 20:31 ` Rich Freeman
2013-01-26 1:51 ` Duncan
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='CAGfcS_=HFVMUBsWnJ-Zua9HxTAXqJ1=C8d3qWL6k=z-pAfhYmw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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