All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: quentin.schulz@cherry.de, Quentin Schulz <foss+yocto@0leil.net>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 1/2] add basic b4 config file
Date: Wed, 05 Feb 2025 13:31:08 +0000	[thread overview]
Message-ID: <c46230cb866a9512e2495e5650ccd0377242e735.camel@linuxfoundation.org> (raw)
In-Reply-To: <5691d776-ffd7-4dbf-b801-f6b66c022dd6@cherry.de>

On Wed, 2025-02-05 at 14:09 +0100, Quentin Schulz via lists.openembedded.org wrote:
> Hi all,
> 
> On 2/3/25 4:17 PM, Quentin Schulz 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. The
> > mid-term/long-term plan is to use patchtest locally.
> > 
> > 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>
> > ---
> >   .b4-config | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/.b4-config b/.b4-config
> > new file mode 100644
> > index 0000000000000000000000000000000000000000..8ec5ddd91e1da05f27a53ff6f3d7351317461859
> > --- /dev/null
> > +++ b/.b4-config
> > @@ -0,0 +1,3 @@
> > +[b4]
> > +  send-series-cc = openembedded-core@lists.openembedded.org
> 
> Messed up here and should be send-series-to instead according to our 
> README.md. Same remark applies to all other b4 patches sent to YP/OE.
> I'll leave a few more days for feedback and send a new version to tackle 
> that oversight.

I merged the script and was about to look at the config files (which
need a little more work by tweaking combo-layer) but I'll hold off
given the issue. I think we're ready to merge them...

Cheers,

Richard


  reply	other threads:[~2025-02-05 13:31 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     ` Richard Purdie [this message]
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
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=c46230cb866a9512e2495e5650ccd0377242e735.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=foss+yocto@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.