linux-ext4.vger.kernel.org archive mirror
 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,
	Matthias Goergens <matthias.goergens@gmail.com>
Subject: [PATCH] MAINTAINERS: name the ext4 dev branch
Date: Wed, 23 Sep 2026 18:17:49 +0800	[thread overview]
Message-ID: <20260923101749.3505886-1-matthias.goergens@gmail.com> (raw)

The ext4 T: entry names the repository without a branch, so tools that
default to the repository's HEAD select master, which still points at a
merge from October 2020 (96485e446260).  Development happens on dev,
which is also the branch linux-next merges.  Name it.

The Sashiko review bot, for one, falls back to HEAD this way and has
been reviewing ext4 patches against that tree.  Its review of an EA
inode refcount fix reported a Critical double decrement and an
undefined function after applying the patch to that stale baseline;
neither holds on dev.

Link: https://lore.kernel.org/all/20260916072420.316321F000FF@smtp.kernel.org/
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/MAINTAINERS b/MAINTAINERS
index 806bd2d80d153..8ed6ae20c2523 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9791,7 +9791,7 @@ L:	linux-ext4@vger.kernel.org
 S:	Maintained
 W:	http://ext4.wiki.kernel.org
 Q:	http://patchwork.ozlabs.org/project/linux-ext4/list/
-T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
 F:	Documentation/filesystems/ext4/
 F:	fs/ext4/
 F:	include/trace/events/ext4.h

base-commit: 9091c97be34083587a75db174aab51551d8e8543
-- 
2.55.0


             reply	other threads:[~2026-09-23 10:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 10:17 Matthias Goergens [this message]
2026-09-23 10:44 ` [PATCH] MAINTAINERS: name the ext4 dev branch 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
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=20260923101749.3505886-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;
as well as URLs for NNTP newsgroup(s).