Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp14888046ybl; Mon, 30 Dec 2019 19:55:31 -0800 (PST) X-Google-Smtp-Source: APXvYqwXyW72K5NNdlJP6UEOG51C+ajEpJGYX1BRaUrJcp/ByCGkDMWQ5FJobv1sDYuKo8Ue0cDI X-Received: by 2002:a9d:4d86:: with SMTP id u6mr55134559otk.42.1577764531006; Mon, 30 Dec 2019 19:55:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1577764530; cv=none; d=google.com; s=arc-20160816; b=cNvEYuolzXDa4lIXeLyR8rawbLjjUJbdiK1YlaG8DnpEzxJH4CdnuHriSLdtWoBVlF iWuDMUWhGRukJLUTfgFkqz8GBv4de4/2CUD50opC2fg2W8P1CjBCIonE55zcWaVfGt// oTzLoie6HircnMP8wkEZP5DyZqn1chRNUESktVAZ282KQIZSaePCb/+djzQGAPhn0qP5 EpXc79puCll6MUmcfIxqSjn7eVxQmxkGnSCy/VIvjIJUeZ8XEfsP9vYC1wiY8XZrcp+O tRfgXHsuZZ+c52e2+hpbllD7vaa811UZDhiCNj31PXwH7y0+bEq2PSKPaKgPNRlv8wmp DwLA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=V70XNnRXsz2/plfnuVMETJq8t+h1QR2lp2LxhR2yWno=; b=x/STGumQ+u9eG+nCx0Ch0yPul8CTrupe+887m3Jz4JG9igViw7u4EZjzO0sPu+voSn 3eAgdiMpjcDP5evY4s9tGD4AaUNd3hRcSpvnExQLeJF9Rs5qIBzQSeUf2OofgZ40/jD9 bW/igVtoIADVJCuqdXW024EtI5mFcoRRw7EANvMlzx7fWsLQfnFKHxpVxIidI7TZzaqy kuuYHJ1ukBLToZ/yeEz2lfDE5KNOPJEVflVzxthUohVWO1aSSb3Uoc0gM/TcHrvnoMLg eJdruIos6XJCeBbLvV6NTyOseTS0W6PvJaXJobnYXCnI2EE3O66icPqYIpjPkl6tYkeg Z2Vw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y186si22930926oig.241.2019.12.30.19.55.18; Mon, 30 Dec 2019 19:55:30 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726502AbfLaDxW (ORCPT + 99 others); Mon, 30 Dec 2019 22:53:22 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:56266 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726312AbfLaDxW (ORCPT ); Mon, 30 Dec 2019 22:53:22 -0500 Received: from viro by ZenIV.linux.org.uk with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1im8at-0003A2-3j; Tue, 31 Dec 2019 03:53:19 +0000 Date: Tue, 31 Dec 2019 03:53:19 +0000 From: Al Viro To: Rob Landley Cc: Randy Dunlap , linux-kernel@vger.kernel.org Subject: Re: Why is CONFIG_VT forced on? Message-ID: <20191231035319.GE4203@ZenIV.linux.org.uk> References: <9b79fb95-f20c-f299-f568-0ffb60305f04@landley.net> <018540ef-0327-78dc-ea5c-a43318f1f640@landley.net> <774dfe49-61a0-0144-42b7-c2cbac150687@landley.net> <20191231024054.GC4203@ZenIV.linux.org.uk> <20191231025255.GD4203@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.1 (2019-06-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 30, 2019 at 09:27:50PM -0600, Rob Landley wrote: > > 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. Where and by whom? > 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. What design discussion? Where? > My mistake. Generally a passive-aggressive flame (complete with comparisons to INTERCAL) and not a shred of reference to any design issues in it tends to be rather ineffecient way to start such discussion... > 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. _I_ have changed??? What the hell? I have never touched kconfig syntax in any way; what are you talking about? Care to post commit IDs in question?