From: Mark Brown <broonie@kernel.org>
To: linux-next@vger.kernel.org,
Thierry Reding <thierry.reding@kernel.org>,
Breno Leitao <leitao@debian.org>
Cc: Mark Brown <broonie@kernel.org>
Subject: [PATCH] next-status: Include a list of trees with duplicate commits
Date: Tue, 11 Aug 2026 18:01:37 +0100 [thread overview]
Message-ID: <20260811170137.319964-1-broonie@kernel.org> (raw)
It's possibly interesting to report trees that are duplicating commits,
this tends to be a combination of trees that routinely cherry pick fixes
instead of merging them up and transient issues with trees that upstream as
patches rather than pull requests.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
next-status | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/next-status b/next-status
index c8aa0eb..7403faf 100755
--- a/next-status
+++ b/next-status
@@ -87,7 +87,12 @@ count_tree_commits()
echo Top trees adding commits to -next: >> ${MSG}
echo >> ${MSG}
-count_tree_commits ${REPORT_SHA1s} 5
+count_tree_commits ${REPORT_SHA1s} 10
+
+echo >> ${MSG}
+echo Trees adding duplicate commits to -next: >> ${MSG}
+(cd ../duplicates/next ; wc -l --total=never *
+ cd ../linus ; wc -l --total=never * ) | sort -nr >> ${MSG}
if [ "${BASELINE}" != "" ]; then
echo >> ${MSG}
--
2.47.3
reply other threads:[~2026-08-11 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260811170137.319964-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=leitao@debian.org \
--cc=linux-next@vger.kernel.org \
--cc=thierry.reding@kernel.org \
/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.