Linux-Next discussions
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Breno Leitao <leitao@debian.org>,
	Thierry Reding <thierry.reding@gmail.com>
Cc: linux-next@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH] merge_msg: Gather the email addresses for the conflicting tree
Date: Thu,  1 Oct 2026 21:49:35 +0100	[thread overview]
Message-ID: <20261001204935.635681-1-broonie@kernel.org> (raw)

We have a list of conflicting trees and the contacts file, do the lookup of
the contacts programatically. Skip doing so for the origin tree since it's
not generally too interesting to tell Linus about these things, and rely on
the sending MUA to deduplicate addresses.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
 merge_msg | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

diff --git a/merge_msg b/merge_msg
index f781e0b..e95cbaa 100755
--- a/merge_msg
+++ b/merge_msg
@@ -46,6 +46,16 @@ if [ "${#hb[@]}" -gt 1 ]; then
 	hbs='s'
 fi
 
+# Rely on the sending MUA to dedupe
+for b in "${hb[@]}"; do
+	if [ "${b}" = "origin" ]; done
+		continue
+	fi
+	bc=$(../tools/get_contacts ${b})
+	IFS=',' read -r -a addrs <<< ${bc}
+	cc+=("${addrs[@]}")
+done
+
 printf -v subject 'manual merge of the BRANCH tree with the %s tree%s' \
 	"${hb[*]}" "$hbs"
 printf -v update 'The BRANCH tree acquired a conflict with the %s tree%s'. \
@@ -72,8 +82,7 @@ if [ "$#" -gt 1 ]; then
 fi
 
 "$tools_dir/message_helper" "${branch[@]}" "$subject" "${cc[@]}" <<EOF
-FIXME: Add owner of second tree to To:
-       Add author(s)/SOB of conflicting commits.
+FIXME: Add author(s)/SOB of conflicting commits.
 
 Today's linux-next merge of the BRANCH tree got $conf in:
 
-- 
2.47.3


             reply	other threads:[~2026-10-01 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-01 20:49 Mark Brown [this message]
2026-10-02 10:28 ` [PATCH] merge_msg: Gather the email addresses for the conflicting tree Breno Leitao
2026-10-02 10:51   ` Mark Brown

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=20261001204935.635681-1-broonie@kernel.org \
    --to=broonie@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-next@vger.kernel.org \
    --cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox