Received: by 10.223.176.5 with SMTP id f5csp1152955wra; Sat, 27 Jan 2018 17:29:40 -0800 (PST) X-Google-Smtp-Source: AH8x225O4zZG8XLNuP2i3/zAd5p6lfp4azbyFXgcPp1YScASShv1jiBILgaJTDCp/20CaDTfdqIO X-Received: by 10.98.153.197 with SMTP id t66mr21239656pfk.142.1517102980729; Sat, 27 Jan 2018 17:29:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517102980; cv=none; d=google.com; s=arc-20160816; b=L1lu1vm/0pO6HCzN+1rGxkJzHEEFSirCLafGA8WaOijysoGb4+5qRMlF7EB82kCCSn 7HynlB8hL5tefUzbGNZ/SOb0aZv4SgM8gLDFuYLUkygD9GrQFdM8GXcVsjkFq0nuhPZk u467iJBlV3QmA/CJNBiDUtkYPf4xE9Hed+izHoymephdyOn+BCMD74i2vpYLGxfMzvTs 9gnm6ItPmyz1bU+JllmVwAH1jstjqE6/wWJLrZuys2lwpgPgnwMPFIFf92wXIFieZN0+ HmZIjoqQlv6ortE5pmmVACEAQaaEkMfsbeNNy9F0SQYRvawNcKSCTaEdvI80N9NTBvVQ ppJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature:dkim-filter :arc-authentication-results; bh=n6luXHKxUp7+AYhunpdXgNR3eXiyU70U0JVuCPOQzsc=; b=Jn2Y9GHSkSp2bY/8qcsD2qgXqMfBct5e17GdkfPLMJZYQ4viLYGpi+jz4TLFJm53i1 Uh1OQ8lJMpPsecvg/8rXVaDZX8NgEvTzcZhX9fiOJfzVQl5gSvLlaPMMoJqlT/otSrGA 2J+LBSMxEzLt3I+pVYFv7GbTrNJAJze/vPmIAeDfUeA2WpvVwlc0FiiuhnV4WunOyA4O tPK6+wSOxeMCzRAfaIMfMXNPJ0mGC9+7Ve8lNL5V6dOVTKq9tFCL3ESloU0xchlWsVrf j2UJZwG/THou0tVy/5cxobjIt61k+7qHalmHRhDWkJPiYdXJiNNeoh6lxbeeK9peLdYK OJQA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=lM9JCH7M; 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 h190si5027703pge.146.2018.01.27.17.29.25; Sat, 27 Jan 2018 17:29:40 -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; dkim=pass header.i=@nifty.com header.s=dec2015msa header.b=lM9JCH7M; 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 S1752496AbeA1B3E (ORCPT + 99 others); Sat, 27 Jan 2018 20:29:04 -0500 Received: from conssluserg-04.nifty.com ([210.131.2.83]:34460 "EHLO conssluserg-04.nifty.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751251AbeA1B3D (ORCPT ); Sat, 27 Jan 2018 20:29:03 -0500 Received: from mail-vk0-f51.google.com (mail-vk0-f51.google.com [209.85.213.51]) (authenticated) by conssluserg-04.nifty.com with ESMTP id w0S1SxTa010113; Sun, 28 Jan 2018 10:28:59 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com w0S1SxTa010113 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.com; s=dec2015msa; t=1517102940; bh=n6luXHKxUp7+AYhunpdXgNR3eXiyU70U0JVuCPOQzsc=; h=In-Reply-To:References:From:Date:Subject:To:Cc:From; b=lM9JCH7MJnB8PqeQLXW7VVFbbeAHKXFa/gUaIlr3YY8yWzfxbfF689CXp5JhISut4 wuAtJrbGluMWzHM2hUtyVko9ZBODC/XfTyCq/8QWf5JybxjK8Zf77Z4+YMVYSSi/r0 1NPpdGNJjN51mwDEULBr0eb0OupP0Myh8cHefb71e1UuauF/mniFTZZhkb1m/rriyf wI/koANJF8/TW26ySHzqdv82C9q7IE4iP2x0kf301iI5dRblUaOL+Pq9ClskNmBhFG YrQsxPAWuj+3s2zlMJ2m2wjk4xkgBfe5B15QHD3BnX6fm477Uv/Pg13zp3r6u/e4JO B+kbyf+bvi/OQ== X-Nifty-SrcIP: [209.85.213.51] Received: by mail-vk0-f51.google.com with SMTP id x203so2484382vkx.10; Sat, 27 Jan 2018 17:28:59 -0800 (PST) X-Gm-Message-State: AKwxyteNW+Pi8u5y6JIUZRGBLoiaJs1qqoc3ZjuwDnqAAPwpdXjhU+sY FrpUFaxL8wMK/39stxieiwi0777hrGi4fTgeW4c= X-Received: by 10.31.130.199 with SMTP id e190mr14404397vkd.34.1517102938722; Sat, 27 Jan 2018 17:28:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.159.49.90 with HTTP; Sat, 27 Jan 2018 17:28:18 -0800 (PST) In-Reply-To: <594ca2cb-5a21-2bba-4132-73d42f3a909a@intel.com> References: <20171219012656.23728-1-marc.herbert@intel.com> <070e7d03-b1a7-430f-709b-bb5fe9e2a0a3@intel.com> <594ca2cb-5a21-2bba-4132-73d42f3a909a@intel.com> From: Masahiro Yamada Date: Sun, 28 Jan 2018 10:28:18 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] Remove silentoldconfig from "make help"; fix kconfig/conf's help To: Marc Herbert Cc: Thiago Macieira , Josh Triplett , Guenter Roeck , Wayne Boyer , Linux Kbuild mailing list , Linux Kernel Mailing List , Michal Marek , Sam Ravnborg Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2018-01-27 8:00 GMT+09:00 Marc Herbert : > Masahiro, > > On 17/01/2018 20:31, Masahiro Yamada wrote: > >> Sorry for my late reply. > > I think we're even now :-) > >>> I'd like to keep that sentence because it's there to explain the legacy and >>> confusing "--silentoldconfig" name which unfortunately still sticks out in >>> the *current* conf.c interface. >>> >>> + printf(" --silentoldconfig Similar to oldconfig but generates configuration in\n" >>> + " include/{generated/,config/} (oldconfig used to be more verbose)\n"); >>> >>> The purpose of this sentence is to warn people that: "silentoldconfig is >>> just archeology, so you can safely ignore it" and save them time. >>> >>> The alternative I considered was to entirely remove "silentconfig" not just >>> from the Makefile's help but from the conf.c help too. > >> >> Another possibility might be to rename 'silentoldconfig'. >> instead of explaining the background in the help message. >> [...] >> It is difficult to suggest a clear name, >> but 'syncconfig' is the one I came up with. >> >> Please suggest if you have a better idea. > > Look like a good idea and name to me but... for a different, bigger > and later commit. > >> Commit fb16d8912db5268f29706010ecafff74b971c58d >> renamed oldnoconfig to olddefconfig... > > ... but it didn't remove any "now internal API" from "make help". Instead it > changed the name of an external and preserved "API". > >> If we worry about the compatibility just in case, >> we can keep 'silentoldconfig' as an alias as well. > > Yes - but later? > > In the meantime I found another instance of silentoldconfig in > Documentation/admin-guide/; posting v3 with that removed too. > I'm also adding some deprecation comments in the source. > > -- Okay, let's go with your patch for now. -- Best Regards Masahiro Yamada