From: Marc Herbert <Marc.Herbert@intel.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Thiago Macieira <thiago.macieira@intel.com>,
Josh Triplett <josh@joshtriplett.org>,
Guenter Roeck <groeck@google.com>,
Wayne Boyer <wayne.boyer@intel.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] Remove silentoldconfig from "make help"; fix kconfig/conf's help
Date: Fri, 12 Jan 2018 14:49:41 -0800 [thread overview]
Message-ID: <f7008e72-e762-a86d-8a39-415eae55dae9@intel.com> (raw)
In-Reply-To: <CAK7LNASR8Qmo85FGr0wW-4t2_uTmDZVSituLLuRm73_+Qqstmw@mail.gmail.com>
Masahiro,
On 09/01/2018 23:17, Masahiro Yamada wrote:
> > "(oldconfig used to be more verbose)"
> The historical background is git.
> If people are interested in archeology,
> they would be able to do it by "git log", "git blame", etc.
> We are generally interested in the current behavior.
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.
Thoughts?
--
Marc
next prev parent reply other threads:[~2018-01-12 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 1:26 [PATCH] Remove silentoldconfig from "make help"; fix kconfig/conf's help Marc Herbert
2018-01-04 17:21 ` Masahiro Yamada
2018-01-05 22:21 ` Marc Herbert
2018-01-10 7:17 ` Masahiro Yamada
2018-01-12 22:49 ` Marc Herbert [this message]
2018-01-18 4:31 ` Masahiro Yamada
2018-01-26 23:00 ` Marc Herbert
2018-01-28 1:28 ` Masahiro Yamada
2018-01-18 1:41 ` [PATCH v2] " Marc Herbert
2018-01-26 22:59 ` [PATCH v3] Remove silentoldconfig from help and docs; " Marc Herbert
2018-01-28 1:40 ` Masahiro Yamada
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=f7008e72-e762-a86d-8a39-415eae55dae9@intel.com \
--to=marc.herbert@intel.com \
--cc=groeck@google.com \
--cc=josh@joshtriplett.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=thiago.macieira@intel.com \
--cc=wayne.boyer@intel.com \
--cc=yamada.masahiro@socionext.com \
/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