From: Thomas Huth <thuth@redhat.com>
To: Christoph Schlameuss <schlameuss@linux.ibm.com>, kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Andrew Jones <andrew.jones@linux.dev>,
Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [kvm-unit-tests PATCH v2 4/4] b4: Add b4 config with default prefix
Date: Mon, 4 May 2026 09:01:06 +0200 [thread overview]
Message-ID: <d90975a4-a141-4d65-816b-0b2c5931493d@redhat.com> (raw)
In-Reply-To: <20260427-b4-cmdline-v2-4-0fea2a50a9d0@linux.ibm.com>
On 27/04/2026 19.36, Christoph Schlameuss wrote:
> b4.send-prefixes adds the prefixes when creating a new patch series.
>
> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
> .b4-config | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/.b4-config b/.b4-config
> new file mode 100644
> index 000000000000..b780cc3d4e6f
> --- /dev/null
> +++ b/.b4-config
> @@ -0,0 +1,2 @@
> +[b4]
> +send-prefixes = kvm-unit-tests
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2026-05-04 7:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 17:36 [kvm-unit-tests PATCH v2 0/4] scripts: Configure and update tools to allow basic b4 usage Christoph Schlameuss
2026-04-27 17:36 ` [kvm-unit-tests PATCH v2 1/4] scripts/checkpatch.pl: Add empty codespell and const_structs configs Christoph Schlameuss
2026-04-27 17:36 ` [kvm-unit-tests PATCH v2 2/4] scripts/checkpatch.pl: Create a project specific codespell config Christoph Schlameuss
2026-04-28 7:42 ` Thomas Huth
2026-04-27 17:36 ` [kvm-unit-tests PATCH v2 3/4] scripts/get_maintainer.pl: Ignore --nogit-chief-penguins option Christoph Schlameuss
2026-05-04 6:53 ` Thomas Huth
2026-04-27 17:36 ` [kvm-unit-tests PATCH v2 4/4] b4: Add b4 config with default prefix Christoph Schlameuss
2026-05-04 7:01 ` Thomas Huth [this message]
2026-05-04 7:07 ` [kvm-unit-tests PATCH v2 0/4] scripts: Configure and update tools to allow basic b4 usage Thomas Huth
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=d90975a4-a141-4d65-816b-0b2c5931493d@redhat.com \
--to=thuth@redhat.com \
--cc=andrew.jones@linux.dev \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=schlameuss@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox