public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Schlameuss <schlameuss@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Huth <thuth@redhat.com>,
	Andrew Jones <andrew.jones@linux.dev>,
	Nicholas Piggin <npiggin@gmail.com>,
	Christoph Schlameuss <schlameuss@linux.ibm.com>
Subject: [kvm-unit-tests PATCH v2 3/4] scripts/get_maintainer.pl: Ignore --nogit-chief-penguins option
Date: Mon, 27 Apr 2026 19:36:45 +0200	[thread overview]
Message-ID: <20260427-b4-cmdline-v2-3-0fea2a50a9d0@linux.ibm.com> (raw)
In-Reply-To: <20260427-b4-cmdline-v2-0-0fea2a50a9d0@linux.ibm.com>

b4 by default calls the get_maintainer.pl script with the
'--nogit-chief-penguins' option letting the 'b4 prep --auto-to-cc' fail.

Adding parsing of that option without any related functionality to allow
simple usage of b4 in the development workflow.

Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>

---

Sorry, I am not too versed with perl, so if there are better ways to fix
this please comment.
---
 scripts/get_maintainer.pl | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
index 117b69145f0e..4d4ff4236f2f 100755
--- a/scripts/get_maintainer.pl
+++ b/scripts/get_maintainer.pl
@@ -31,6 +31,7 @@ my $email_fixes = 1;
 my $email_list = 1;
 my $email_moderated_list = 1;
 my $email_subscriber_list = 0;
+my $email_git_penguin_chiefs = 0;
 my $email_git = 0;
 my $email_git_all_signature_types = 0;
 my $email_git_blame = 0;
@@ -228,6 +229,7 @@ if (!GetOptions(
 		'git-blame!' => \$email_git_blame,
 		'git-blame-signatures!' => \$email_git_blame_signatures,
 		'git-fallback!' => \$email_git_fallback,
+		'git-chief-penguins!' => \$email_git_penguin_chiefs,
 		'git-min-signatures=i' => \$email_git_min_signatures,
 		'git-max-maintainers=i' => \$email_git_max_maintainers,
 		'git-min-percent=i' => \$email_git_min_percent,

-- 
2.53.0


  parent reply	other threads:[~2026-04-27 17:37 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 ` Christoph Schlameuss [this message]
2026-05-04  6:53   ` [kvm-unit-tests PATCH v2 3/4] scripts/get_maintainer.pl: Ignore --nogit-chief-penguins option 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
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=20260427-b4-cmdline-v2-3-0fea2a50a9d0@linux.ibm.com \
    --to=schlameuss@linux.ibm.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=thuth@redhat.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