From: Chao Yu <chao@kernel.org>
To: xiang@kernel.org
Cc: chao@kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: erofs: add dev branch to git tree entry
Date: Sun, 11 Oct 2026 07:44:31 +0800 [thread overview]
Message-ID: <0b7f00ae-29ca-48e4-83f8-eec0213e3535@kernel.org> (raw)
In-Reply-To: <asqt-vM6LOPyqz_p@XiangdeMacBook-Pro.local>
On 10/11/26 05:28, Gao Xiang wrote:
> On Sat, Oct 10, 2026 at 03:06:23PM +0800, Chao Yu wrote:
>> 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>
>
> Acked-by: Gao Xiang <xiang@kernel.org>
>
>
> Hi Chao,
>
> BTW, could we request sashiko folks adding erofs mailing list
> to their review list as well?
>
> Since some patch could not Cc LKML or fsdevel, but I guess
> we need them to be reviewed by sashiko too.
Xiang,
Agreed, let me submit a patch for erofs.
Note that by default it's mute (it won't reply review comment back to anyone), so
author or reviewer needs to check comments from sashiko in its UI (https://sashiko.dev/),
but we can change the config if we want to receive review email from sashiko.
Thanks,
>
> Thanks,
> Gao Xiang
prev parent reply other threads:[~2026-10-10 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 7:06 Chao Yu
2026-10-10 21:28 ` Gao Xiang
2026-10-10 23:44 ` Chao Yu [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=0b7f00ae-29ca-48e4-83f8-eec0213e3535@kernel.org \
--to=chao@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiang@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
all inboxes | Powered by JetHome®