All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: tools@linux.kernel.org
Subject: b4 prep-perpatch-check-cmd conf via .b4-config
Date: Thu, 23 May 2024 10:50:05 +0200	[thread overview]
Message-ID: <87sey8yksi.fsf@baylibre.com> (raw)

Hi,

I'm yet another (very) happy user of b4.
Thank you for developping and maintaining it.

I've noticed that v0.14+ contains the new b4 prep --check command.

This can be customized via b4.prep-perpatch-check-cmd [1]
However, we cannot customize this via a project specific .b4-config [2]
file.

It would be useful to be able to customize this via .b4-config, for
example to invoke checkpatch.pl with additional arguments (on a
per-project basis).

For example, in U-Boot, I would have the following .b4-config:
[b4]
prep-perpatch-check-cmd = ./scripts/checkpatch.pl -q --terse --no-summary --mailback --u-boot --showfile

Looking at _setup_main_config(), I can see that wtglobs does not contain
'prep-*', but adding it seems not sufficient, probably due to multivals
parsing.

I don't have enough knowledge/time to dive deeper on this, but could we
consider adding support for configuring prep-perpatch-check-cmd in
.b4-config?

Thank you!
Mattijs

[1] https://b4.docs.kernel.org/en/latest/config.html#contributor-oriented-settings
[2] https://b4.docs.kernel.org/en/latest/config.html#per-project-defaults

             reply	other threads:[~2024-05-23  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  8:50 Mattijs Korpershoek [this message]
2024-05-23  9:45 ` b4 prep-perpatch-check-cmd conf via .b4-config Matthieu Baerts
2024-05-23  9:58   ` Mattijs Korpershoek
2024-05-23 12:25     ` Konstantin Ryabitsev
2024-05-23 12:30 ` Kernel.org Bugbot
2024-05-30 15:30 ` Kernel.org Bugbot

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=87sey8yksi.fsf@baylibre.com \
    --to=mkorpershoek@baylibre.com \
    --cc=tools@linux.kernel.org \
    /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.