From: Quentin Schulz <quentin.schulz@cherry.de>
To: Khem Raj <raj.khem@gmail.com>, foss@0leil.net
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 0/2] add basic b4 config file
Date: Tue, 4 Feb 2025 10:13:41 +0100 [thread overview]
Message-ID: <cd355530-d72b-476e-9c99-bc53f0a3a337@cherry.de> (raw)
In-Reply-To: <CAMKF1sqh0VMORr2ivhz82XVt7EuZ_UmUgtFVHOXb0pQwDesnnw@mail.gmail.com>
Hi Khem,
On 2/3/25 8:42 PM, Khem Raj wrote:
> On Mon, Feb 3, 2025 at 7:18 AM Quentin Schulz via
> lists.openembedded.org <foss=0leil.net@lists.openembedded.org> wrote:
>>
>> This adds very basic support for using b4 in OE-Core. This essentially
>> just automatically adds the proper mailing list when running b4 prep
>> --auto-to-cc.
>>
>> This also adds the b4 wrapper script that poky will need to use in order
>> to identify which mailing list a patch needs to be sent to and do some
>> additional per-patch checks that aren't necessary when running from
>> vanilla OE-Core.
>>
>> Once this is merged, poky will need to merge OE-Core into itself and
>> override with its own .b4-config that makes use of that script.
>>
>> Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
>> ---
>> Changes in v2:
>> - add mention to first patch that running patchtest for b4 prep --check
>> is what we're eventually aiming for,
>> - add poky b4 wrapper script (it used to be in the patch series for
>> poky, c.f. https://lore.kernel.org/poky/20250123-b4-support-v1-1-4841f52eccbb@cherry.de/T/#m95d6aa25cc42352416da477cf07d7b3cbd671231
>> - poky b4 wrapper script properly identifies patches with files modified
>> in both OE-Core and other repos part of poky,
>> - poky b4 wrapper script pretty prints when there's more than one
>> project modified by a script, instead of lazily printing a Python
>> list,
>> - Link to v1: https://lore.kernel.org/r/20250117-b4-support-v1-1-fe74a5f50eb6@cherry.de
>>
>> ---
>> Quentin Schulz (2):
>> add basic b4 config file
>> scripts: add b4-wrapper for poky
>>
>> .b4-config | 3 +
>> scripts/b4-wrapper-poky.py | 170 +++++++++++++++++++++++++++++++++++++++++++++
>
> is there anything specific to poky in this script ? if not then it
> should not use that in name, it will
Yes it is poky specific...
> make it confusing. In oe-core we do not refer to particular distros if
> not needed.
>
...git-repo poky specific, not poky distro specific. Do you have
something better to suggest than this?
Cheers,
Quentin
next prev parent reply other threads:[~2025-02-04 9:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 15:17 [PATCH v2 0/2] add basic b4 config file Quentin Schulz
2025-02-03 15:17 ` [PATCH v2 1/2] " Quentin Schulz
2025-02-03 15:31 ` Patchtest results for " patchtest
2025-02-05 13:09 ` Quentin Schulz
2025-02-05 13:31 ` [OE-core] " Richard Purdie
2025-02-03 15:17 ` [PATCH v2 2/2] scripts: add b4-wrapper for poky Quentin Schulz
2025-02-03 19:42 ` [OE-core] [PATCH v2 0/2] add basic b4 config file Khem Raj
2025-02-04 9:13 ` Quentin Schulz [this message]
2025-02-04 9:44 ` Richard Purdie
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=cd355530-d72b-476e-9c99-bc53f0a3a337@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=foss@0leil.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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.