From: Randy Dunlap <rdunlap@infradead.org>
To: Jesse T <mr.bossman075@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] kconfig: menuconfig: remove jump_key::index
Date: Fri, 30 Jun 2023 21:23:00 -0700 [thread overview]
Message-ID: <e98fdf36-92bb-2655-41dc-6e31eb128f37@infradead.org> (raw)
In-Reply-To: <CAJFTR8Txd-6-=5RSoHhgg1a6mr4rEAUv2Ta1F5OLsC3NC4U-Sw@mail.gmail.com>
Hi Jesse,
On 6/30/23 21:08, Jesse T wrote:
> On Thu, Jun 29, 2023 at 12:03 PM Masahiro Yamada <masahiroy@kernel.org> wrote:
>>
>> You do not need to remember the index of each jump key because you can
>> count it up after a key is pressed.
>>
>> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
>> ---
>
> One slight off-topic question.
> The names of the menu-based config programs have names similar to their
> corresponding file gconfig ('gconf'), xconfig ('qconf'), menuconfig ('mconf'),
> and nconfig ('nconf'). The only exceptions to this one-letter naming are mconfig
> is not memuconfig and qconfig isn't xconfig. Would it be possible to
> add an alias
> to fix this?
>
> Side-side note config isn't in the docs.
I'm not following what you mean here.
Are you referring to 'make config'?
So: what documentation is missing and where would it be found?
thanks.
--
~Randy
next prev parent reply other threads:[~2023-07-01 4:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 16:03 [PATCH 1/2] kconfig: menuconfig: simplify global jump key assignment Masahiro Yamada
2023-06-29 16:03 ` [PATCH 2/2] kconfig: menuconfig: remove jump_key::index Masahiro Yamada
2023-07-01 4:08 ` Jesse T
2023-07-01 4:23 ` Randy Dunlap [this message]
2023-07-01 4:38 ` Jesse T
2023-07-01 4:43 ` Randy Dunlap
2023-07-02 15:27 ` Masahiro Yamada
2023-07-01 3:57 ` [PATCH 1/2] kconfig: menuconfig: simplify global jump key assignment Jesse T
2023-07-02 15:09 ` Masahiro Yamada
2023-07-02 19:32 ` Jesse T
2023-07-02 20:26 ` Jesse T
2023-07-12 17:39 ` Jesse T
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=e98fdf36-92bb-2655-41dc-6e31eb128f37@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mr.bossman075@gmail.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
all inboxes | Powered by JetHome®