From: Rob Landley <rob@landley.net>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Why is CONFIG_VT forced on?
Date: Mon, 30 Dec 2019 21:27:50 -0600 [thread overview]
Message-ID: <ffa8ec1d-71d7-a153-eed9-8e2daee40949@landley.net> (raw)
In-Reply-To: <20191231025255.GD4203@ZenIV.linux.org.uk>
On 12/30/19 8:52 PM, Al Viro wrote:
>> Rob, if you are in a mood for a long wank, it's your business. But try to avoid
>> spraying the results over public lists.
I don't post regularly here anymore, but it's good to see the code of conduct
and Linus's sabbatical have had a positive effect on the place in my absence.
> To elaborate: you are complaining about VT being treated the same way as e.g.
> ELF_CORE or UID16. Which might or might not be reasonable, but kconfig folks
> have nothing to do with that.
>
> Your complaint is basically that the same thing is forcing all of those on
> in default configs.
No, my complaint was that kconfig basically has the concept of symbols that turn
_off_ something that is otherwise on by default ("Disable X" instead of "Enable
X"), but it was implemented it in an awkward way then allowed to scale to silly
levels, and now the fact it exists is being used as evidence that it was a good
idea.
I had to work out a way to work around this design breakage, which I did and had
moved on before this email, but I thought pointing out the awkwardness might
help a design discussion. My mistake.
The thread _started_ because menuconfig help has a blind spot (which seemed like
a bug to me, it _used_ to say why), and then I found the syntax you changed a
year or two back non-obvious when I tried to RTFM but that part got answered.
> Instead of having a separate ROB_WANTS_THOSE that would
> prop the rest, but not VT (and frankly, quite a bit of that rest is
> questionable for minimal setups). With ROB_WANTS_THOSE (or equivalent
> information) enshrined in the kernel tree for your convenience.
>
> Pardon me, but... why is that anyone else's problem?
You drove everybody away who would express similar concerns years ago. None of
my co-workers have wanted to get linux-kernel on them in ages. (I thought that
sort of thing was why you were having a code of conduct and such, but apparently
not.)
*shrug* I'll try to be more proactive about stripping linux-kernel from the cc:
list once I've got a human's attention in a thread. (Or just try to dig up
somebody to email directly via git history and the maintainers file.)
I leave you to your sexual metaphors,
Rob
next prev parent reply other threads:[~2019-12-31 3:24 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 0:30 Rob Landley
2019-12-31 0:36 ` Randy Dunlap
2019-12-31 0:53 ` Rob Landley
2019-12-31 0:59 ` Randy Dunlap
2019-12-31 1:45 ` Rob Landley
2019-12-31 2:00 ` Randy Dunlap
2019-12-31 2:04 ` Rob Landley
2019-12-31 2:03 ` Randy Dunlap
2019-12-31 2:33 ` Theodore Y. Ts'o
2019-12-31 2:40 ` Al Viro
2019-12-31 2:52 ` Al Viro
2019-12-31 3:27 ` Rob Landley [this message]
2019-12-31 3:53 ` Al Viro
2019-12-31 4:18 ` Al Viro
2019-12-31 5:58 ` Al Viro
2020-01-01 20:41 ` [PATCH] menuconfig: restore prompt dependencies in help text Arvind Sankar
2020-01-01 21:04 ` Al Viro
2020-01-01 22:26 ` Arvind Sankar
2020-01-02 16:14 ` Randy Dunlap
2020-01-02 23:14 ` [PATCH] kconfig: " Arvind Sankar
2020-01-03 2:10 ` Masahiro Yamada
2020-01-03 4:20 ` Arvind Sankar
2019-12-31 1:55 ` Why is CONFIG_VT forced on? Theodore Y. Ts'o
2020-01-04 20:27 ` Enrico Weigelt, metux IT consult
2019-12-31 2:28 ` Al Viro
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=ffa8ec1d-71d7-a153-eed9-8e2daee40949@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@zeniv.linux.org.uk \
/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®