Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230629160351.2996541-1-masahiroy@kernel.org>
 <20230629160351.2996541-2-masahiroy@kernel.org> <CAJFTR8Txd-6-=5RSoHhgg1a6mr4rEAUv2Ta1F5OLsC3NC4U-Sw@mail.gmail.com>
 <e98fdf36-92bb-2655-41dc-6e31eb128f37@infradead.org>
In-Reply-To: <e98fdf36-92bb-2655-41dc-6e31eb128f37@infradead.org>
From:   Jesse T <mr.bossman075@gmail.com>
Date:   Sat, 1 Jul 2023 00:38:33 -0400
Message-ID: <CAJFTR8QgYykuEq_AkODEWPUYXncKgRBHOncxT=ypZTQODkyarw@mail.gmail.com>
Subject: Re: [PATCH 2/2] kconfig: menuconfig: remove jump_key::index
To:     Randy Dunlap <rdunlap@infradead.org>
Cc:     Masahiro Yamada <masahiroy@kernel.org>,
        linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, Jul 1, 2023 at 12:23=E2=80=AFAM Randy Dunlap <rdunlap@infradead.org=
> wrote:
>
> Hi Jesse,
>
> On 6/30/23 21:08, Jesse T wrote:
> > On Thu, Jun 29, 2023 at 12:03=E2=80=AFPM Masahiro Yamada <masahiroy@ker=
nel.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 ('m=
conf'),
> > and nconfig ('nconf'). The only exceptions to this one-letter naming ar=
e 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'?

Typo sorry, `make gconfig`
It's not listed at the top Documentation/kbuild/kconfig.rst and only briefl=
y
mentioned at the bottom.

>
> So: what documentation is missing and where would it be found?
>
> thanks.
> --
> ~Randy