From: patchwork-bot+f2fs@kernel.org
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-fscrypt@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [f2fs-dev] [PATCH] MAINTAINERS: update fscrypt git repo
Date: Tue, 28 Feb 2023 01:01:55 +0000 [thread overview]
Message-ID: <167754611503.27916.4447364691434133144.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230116233424.65657-1-ebiggers@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Eric Biggers <ebiggers@google.com>:
On Mon, 16 Jan 2023 15:34:24 -0800 you wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> fscrypt.git is being renamed to linux.git, so update MAINTAINERS
> accordingly. (The reasons for the rename are to match what I'm doing
> for the new fsverity repo, which also involves the branch names changing
> to be clearer; and to avoid ambiguity with userspace tools.)
>
> [...]
Here is the summary with links:
- [f2fs-dev] MAINTAINERS: update fscrypt git repo
https://git.kernel.org/jaegeuk/f2fs/c/31e1be62abde
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:[~2023-02-28 1:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 23:34 [f2fs-dev] [PATCH] MAINTAINERS: update fscrypt git repo Eric Biggers
2023-02-28 1:01 ` patchwork-bot+f2fs [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=167754611503.27916.4447364691434133144.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).