Linux EXT4 FS development
 help / color / mirror / Atom feed
From: Matthias Goergens <matthias.goergens@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: name the ext4 dev branch
Date: Thu,  1 Oct 2026 19:25:40 +0800	[thread overview]
Message-ID: <20261001112540.3822983-1-matthias.goergens@gmail.com> (raw)
In-Reply-To: <20260924033200.3615554-1-matthias.goergens@gmail.com>

Hi Ted,

A short report on how the T: cleanup went, as promised.

The documentation patch is at v2 [1].  It now only describes the
syntax: a git T: entry may name a branch, or an entry may have several
T: lines, and what each branch is for is left to the subsystem's P:
profile or the maintainer.  Niklas Cassel, Krzysztof Kozlowski and Eric
Biggers reviewed it and Marc Zyngier acked it; no word from Jon yet.

I sent one patch each to 18 repositories, a few a day.  Three were
picked up (libata, clk, mfd), three have acks or reviews (ext4, phy,
fbdev), six had no reply, and the rest I withdrew or am withdrawing.
Most objections came down to two points.  One branch cannot describe a
tree with both a fixes and a next branch (Greg Kroah-Hartman, Guenter
Roeck).  And several maintainers want contributors to start from
mainline, not from their next branch (Fan Wu, Marc Zyngier); Petr
Mladek and Miroslav Benes added that T: names a repository, and that
review tools should get their own pointer if they need one.

The trigger was Sashiko, the AI review bot, reviewing against a
repository's default branch even when mainline had long since merged
it.  That is now fixed in Sashiko itself: since 28 September it skips
such a branch and uses linux-next.  So I am not sending the 46 further
patches I had prepared.

For ext4 the patch is still correct, but no tool needs it any more, so
take it only if you want it there for people; dropping it is fine.

[1] https://lore.kernel.org/all/20260925120047.1093617-1-matthias.goergens@gmail.com/

Thanks,
Matthias

  parent reply	other threads:[~2026-10-01 11:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 10:17 [PATCH] MAINTAINERS: name the ext4 dev branch Matthias Goergens
2026-09-23 10:44 ` Jan Kara
2026-09-24  3:14 ` Theodore Tso
2026-09-24  3:32   ` Matthias Goergens
2026-09-24  4:00     ` Eric Biggers
2026-09-24  8:30       ` Matthias Goergens
2026-09-24  8:53       ` Jan Kara
2026-09-25 13:06       ` Niklas Cassel
2026-09-25 18:43         ` Eric Biggers
2026-09-26  6:11         ` Matthias Goergens
2026-09-26 15:57           ` Niklas Cassel
2026-10-01 11:25     ` Matthias Goergens [this message]
2026-10-08 15:32 ` Theodore Ts'o

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=20261001112540.3822983-1-matthias.goergens@gmail.com \
    --to=matthias.goergens@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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