Re: b4 prep-perpatch-check-cmd conf via .b4-config

[Mattijs Korpershoek <mkorpershoek@baylibre.com>]

Hi Matthieu,

Thank you for your reply.

On jeu., mai 23, 2024 at 11:45, Matthieu Baerts <matttbe@kernel.org> wrote:

> Hi Mattijs,
>
> On 23/05/2024 10:50, Mattijs Korpershoek wrote:
>
> (...)
>
>> 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.
>
> Even if it is would be handy, this feature has been explicitly removed
> for security reasons:
>
>   https://git.kernel.org/pub/scm/utils/b4/b4.git/commit/?id=a1360385

Ah indeed, I missed that. Seems like a sane reason to not allow this.

>
> There could be a solution similar to 'direnv' where a 'b4 allow' command
> would mark a version of '.b4-config' as trusted, e.g. by adding a
> checksum in the local git config and checking it before reading the
> config file?

Maybe that's a better idea.
Since you pointed using local git config, I actually gave this another
thought and I can solve my problem by using a project specific git config:

$ cd ~/work/upstream/u-boot
$ git config b4.prep-perpatch-check-cmd './scripts/checkpatch.pl -q --terse --no-summary --mailback --u-boot --showfile'

Thanks for pointing me in the right direction!

Mattijs

>
> Cheers,
> Matt
> -- 
> Sponsored by the NGI0 Core fund.