From: Breno Leitao <leitao@debian.org>
To: Mark Brown <broonie@kernel.org>
Cc: ksummit@lists.linux.dev,
Thierry Reding <thierry.reding@kernel.org>,
linux-next@vger.kernel.org
Subject: Re: [MAINTAINERS SUMMIT] Any feedback for -next?
Date: Wed, 12 Aug 2026 04:42:21 -0700 [thread overview]
Message-ID: <anxaYg9XL7nD9w40@gmail.com> (raw)
In-Reply-To: <1025da50-3e21-43c7-a761-4f65ed5e5069@sirena.org.uk>
On Tue, Aug 11, 2026 at 05:54:59PM +0100, Mark Brown wrote:
> Any other ideas?
I'm new to this area, so please forgive what might be a silly
question: would it make sense for maintainers' -next trees to keep
a stable git history?
Some maintainer trees are already stable and append-only, which
gives linux-next users/testers stable commits to point to, instead
of ephemeral commits that can disappear later due to history
rewrites.
Would getting rid of these ephemeral commits make linux-next easier
to work with?
prev parent reply other threads:[~2026-08-12 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 16:54 [MAINTAINERS SUMMIT] Any feedback for -next? Mark Brown
2026-08-11 19:31 ` Geert Uytterhoeven
2026-08-12 11:19 ` Uwe Kleine-König
2026-08-12 11:42 ` 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=anxaYg9XL7nD9w40@gmail.com \
--to=leitao@debian.org \
--cc=broonie@kernel.org \
--cc=ksummit@lists.linux.dev \
--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.