Linux-Next discussions
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-next@vger.kernel.org, Thierry Reding <thierry.reding@kernel.org>
Subject: Re: [PATCH] next-status: Include a list of trees with duplicate commits
Date: Wed, 12 Aug 2026 06:34:30 -0700	[thread overview]
Message-ID: <anx2Wd2wtQXNNexy@gmail.com> (raw)
In-Reply-To: <20260811170137.319964-1-broonie@kernel.org>

On Tue, Aug 11, 2026 at 06:01:37PM +0100, Mark Brown wrote:
> 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>

Reviewed-by: Breno Leitao <leitao@debian.org>

      reply	other threads:[~2026-08-12 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 17:01 [PATCH] next-status: Include a list of trees with duplicate commits Mark Brown
2026-08-12 13:34 ` Breno Leitao [this message]

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=anx2Wd2wtQXNNexy@gmail.com \
    --to=leitao@debian.org \
    --cc=broonie@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox