From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] MAINTAINERS: f2fs: add dev branch to git tree entry
Date: Tue, 13 Oct 2026 22:30:30 +0000 [thread overview]
Message-ID: <179193063051.1493834.11557943978794677204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261010065946.1763794-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Sat, 10 Oct 2026 14:59:46 +0800 you wrote:
> From: Chao Yu <chao@kernel.org>
>
> The F2FS 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.
>
> [...]
Here is the summary with links:
- [f2fs-dev] MAINTAINERS: f2fs: add dev branch to git tree entry
https://git.kernel.org/jaegeuk/f2fs/c/beafa2721b63
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2026-10-13 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 6:59 [f2fs-dev] [PATCH] MAINTAINERS: f2fs: add dev branch to git tree entry Chao Yu via Linux-f2fs-devel
2026-10-13 22:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [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=179193063051.1493834.11557943978794677204.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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.