From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Cc: Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH v2 03/11] patman: Add a .patman-defaults file for U-Boot
Date: Sun, 5 Jul 2026 13:32:14 -0600 [thread overview]
Message-ID: <20260705193251.2190705-4-sjg@chromium.org> (raw)
In-Reply-To: <20260705193251.2190705-1-sjg@chromium.org>
patman is now installed from the separate patch-manager package. It reads
a .patman-defaults file from the tree root as its lowest-priority config,
so a project can ship defaults that developers still override from their
own ~/.patman, a local .patman or the command line. This behaviour is new
in patman version 0.0.20
Add one for U-Boot, alongside .b4-config, pinning the patchwork server and
the get_maintainer.pl invocation so the tool works out of the box without
depending on patman's built-in defaults. A few other settings are listed,
commented out, as a starting point.
Signed-off-by: Simon Glass <sjg@chromium.org>
---
Changes in v2:
- New patch: add a .patman-defaults file for the external patman tool
.patman-defaults | 32 ++++++++++++++++++++++++++++++++
1 file changed, 32 insertions(+)
create mode 100644 .patman-defaults
diff --git a/.patman-defaults b/.patman-defaults
new file mode 100644
index 00000000000..6b6063b05f4
--- /dev/null
+++ b/.patman-defaults
@@ -0,0 +1,32 @@
+# Default patman settings for the U-Boot tree
+#
+# patman is maintained separately; install it with:
+# pip install patch-manager
+#
+# See https://deinde.dev/patman
+#
+# patman reads this file at the lowest priority, so anything set here is a
+# default that you can override in your own ~/.patman, in a local .patman or
+# on the command line. patman autodetects the U-Boot project and locates
+# scripts/get_maintainer.pl on its own; the patchwork server and get-maintainer
+# script are pinned here so U-Boot does not depend on patman's built-in
+# defaults in case those change.
+
+[settings]
+patchwork_url: https://patchwork.ozlabs.org
+get_maintainer_script: scripts/get_maintainer.pl --norolestats
+
+# Other settings you might set here as project defaults:
+# process_tags: True
+# add_signoff: True
+# check_patch: True
+# verbose: False
+# smtp_server: /path/to/sendmail
+
+# Aliases are recursive and are usually kept per-user in ~/.patman:
+# [alias]
+# me: Your Name <you@example.com>
+
+# Addresses known to bounce can be dropped from the recipient list:
+# [bounces]
+# someone: A Name <someone@example.com>
--
2.43.0
next prev parent reply other threads:[~2026-07-05 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 19:32 [PATCH v2 00/11] Remove patman from the U-Boot tree Simon Glass
2026-07-05 19:32 ` [PATCH v2 01/11] doc: Move the b4 guide into sending_patches Simon Glass
2026-07-05 20:26 ` Tom Rini
2026-07-06 11:59 ` Mattijs Korpershoek
2026-07-05 19:32 ` [PATCH v2 02/11] doc: Remove the patman documentation Simon Glass
2026-07-05 20:26 ` Tom Rini
2026-07-06 12:00 ` Mattijs Korpershoek
2026-07-05 19:32 ` Simon Glass [this message]
2026-07-05 20:26 ` [PATCH v2 03/11] patman: Add a .patman-defaults file for U-Boot Tom Rini
2026-07-05 19:32 ` [PATCH v2 04/11] patman: Replace the tool with a stub for patch-manager Simon Glass
2026-07-05 19:32 ` [PATCH v2 05/11] patman: Remove the test suite Simon Glass
2026-07-05 19:32 ` [PATCH v2 06/11] patman: Remove the patch-management code Simon Glass
2026-07-05 19:32 ` [PATCH v2 07/11] CI: Install pylibfdt's requirements in the tool jobs Simon Glass
2026-07-05 20:26 ` Tom Rini
2026-07-05 19:32 ` [PATCH v2 08/11] CI: Stop building and testing patman Simon Glass
2026-07-05 20:27 ` Tom Rini
2026-07-05 19:32 ` [PATCH v2 09/11] tools: docker: Drop patman from the CI image Simon Glass
2026-07-05 19:32 ` [PATCH v2 10/11] tools: Stop packaging patman as a pip module Simon Glass
2026-07-05 19:32 ` [PATCH v2 11/11] test: Stop running the patman tests Simon Glass
2026-07-06 16:40 ` [PATCH v2 00/11] Remove patman from the U-Boot tree Tom Rini
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=20260705193251.2190705-4-sjg@chromium.org \
--to=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.