From: Nathan Chancellor <nathan@kernel.org>
To: Julian Braha <julianbraha@gmail.com>
Cc: Erkan Erdem <hexvalid@gmail.com>, Nicolas Schier <nsc@kernel.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Ariel Marcovitch <arielmarcovitch@gmail.com>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2] checkkconfigsymbols: resolve revisions before resetting the tree
Date: Tue, 15 Sep 2026 16:36:06 -0700 [thread overview]
Message-ID: <20260915233606.GA863881@ax162> (raw)
In-Reply-To: <0122859e-028d-4860-b2ea-dcd709e4c505@gmail.com>
On Tue, Sep 15, 2026 at 12:43:29PM +0100, Julian Braha wrote:
> On 9/7/26 11:37, Erkan Erdem wrote:
> > The same problem affects --commit with the current branch name.
> >
> > Fixes: b1a3f243485f ("checkkconfigsymbols.py: make it Git aware")
>
> While it's good to support this, I don't think the Fixes tag is
> appropriate here, because this wasn't really a bug... it was just
> unsupported functionality.
I guess it is because neither this change nor the below change did not
take care of disallowing the branch name with '--commit'. That said, I
do agree that I think a Fixes is a little superfluous here, I would
leave it off of future revisions.
> > Link: https://lore.kernel.org/20210901145212.478066-1-arielmarcovitch@gmail.com/
>
> This commit added a check that will cause the script to exit if
> 'HEAD...' is passed to --commit. So it seems like this patch should also
> remove those lines now.
While I do agree that we should revert this change, which is
d62d5aed3354 ("checkkconfigsymbols.py: Forbid passing 'HEAD' to --commit")
in the tree, I think it would be better done as a separate commit, whose
justification is that HEAD is now properly resolved as a result of this
change.
--
Cheers,
Nathan
prev parent reply other threads:[~2026-09-15 23:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:37 [PATCH v2] checkkconfigsymbols: resolve revisions before resetting the tree Erkan Erdem
2026-09-15 11:43 ` Julian Braha
2026-09-15 23:36 ` Nathan Chancellor [this message]
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=20260915233606.GA863881@ax162 \
--to=nathan@kernel.org \
--cc=arielmarcovitch@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hexvalid@gmail.com \
--cc=julianbraha@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nsc@kernel.org \
--cc=valentinrothberg@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.