From: Chao Yu <chao@kernel.org>
To: xiang@kernel.org
Cc: linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <lihongbo22@huawei.com>,
Chunhai Guo <guochunhai@vivo.com>, Chao Yu <chao@kernel.org>
Subject: [PATCH] MAINTAINERS: erofs: add dev branch to git tree entry
Date: Sat, 10 Oct 2026 15:06:23 +0800 [thread overview]
Message-ID: <20261010070623.1766952-1-chao@kernel.org> (raw)
From: Chao Yu <chao@kernel.org>
The EROFS entry lists the git tree without a branch, so tools that
derive a baseline from MAINTAINERS, e.g. sashiko, fall back to the
remote HEAD, which points to master. master only moves at -rc1, so
series developed against the dev branch fail to apply there.
Name the dev branch explicitly, where erofs patches are queued.
Signed-off-by: Chao Yu <chao@kernel.org>
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 068beaa035ac..63c8de75ada9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -9690,7 +9690,7 @@ R: Chunhai Guo <guochunhai@vivo.com>
L: linux-erofs@lists.ozlabs.org
S: Maintained
W: https://erofs.docs.kernel.org
-T: git git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git
+T: git git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs.git dev
F: Documentation/ABI/testing/sysfs-fs-erofs
F: Documentation/filesystems/erofs.rst
F: fs/erofs/
--
2.49.0
next reply other threads:[~2026-10-10 7:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 7:06 Chao Yu [this message]
2026-10-10 21:28 ` [PATCH] MAINTAINERS: erofs: add dev branch to git tree entry Gao Xiang
2026-10-10 23:44 ` Chao Yu
2026-10-14 6:30 ` Chao Yu
2026-10-14 11:29 ` Gao Xiang
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=20261010070623.1766952-1-chao@kernel.org \
--to=chao@kernel.org \
--cc=dhavale@google.com \
--cc=guochunhai@vivo.com \
--cc=jefflexu@linux.alibaba.com \
--cc=lihongbo22@huawei.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.com \
/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