From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: foss@0leil.net, openembedded-core@lists.openembedded.org
Cc: Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [OE-core] [PATCH] add basic b4 config file
Date: Thu, 23 Jan 2025 15:06:58 +0000 [thread overview]
Message-ID: <2e7ba5852015b3bc94c6e4a7d0acae2169ac0bdf.camel@linuxfoundation.org> (raw)
In-Reply-To: <20250117-b4-support-v1-1-fe74a5f50eb6@cherry.de>
On Fri, 2025-01-17 at 12:59 +0100, Quentin Schulz via lists.openembedded.org wrote:
> From: Quentin Schulz <quentin.schulz@cherry.de>
>
> b4[1] is a very nice tool for mail-based contribution. A config[2] file
> exists to set up a few defaults. We can use it to set the Cc recipients
> to always add, in our case the mailing list.
>
> Because we do not have anything to check for now, disable needs-checking
> so patches can be sent without running b4 prep --check.
>
> Because we do not have any auto-to-cc support (and the implicit one
> using scripts/get_maintainer.pl cannot work for us), also disable
> needs-auto-to-cc so patches can be sent without running b4 prep
> --auto-to-cc.
>
> [1] https://pypi.org/project/b4/
> [2] https://b4.docs.kernel.org/en/latest/config.html
>
> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
> ---
> Note that this file should be overridden by the one that I'll send for
> poky by the merging script (no clue how that would work), i.e. an update
> of .b4-config from OE-Core should not override the one from poky OE-Core
> when we merge/cherry-pick OE-Core patches later on.
Did you send one for poky? I was waiting to see what that looked like
so I could work out how to handle files. There are ways to do that but
I could do with knowing how things will ultimately look before I merge
anything.
Cheers,
Richard
next prev parent reply other threads:[~2025-01-23 15:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 11:59 [PATCH] add basic b4 config file Quentin Schulz
2025-01-17 12:16 ` Patchtest results for " patchtest
2025-01-23 15:06 ` Richard Purdie [this message]
2025-01-23 15:39 ` [OE-core] " Quentin Schulz
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=2e7ba5852015b3bc94c6e4a7d0acae2169ac0bdf.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=foss@0leil.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/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.