From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-next@vger.kernel.org, "Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-fscrypt@vger.kernel.org, fsverity@lists.linux.dev
Subject: Re: Please update fscrypt and fsverity branches in linux-next
Date: Wed, 25 Jan 2023 15:48:18 +1100 [thread overview]
Message-ID: <20230125154818.671047ae@canb.auug.org.au> (raw)
In-Reply-To: <Y9BRoE/SIg1aUh+P@sol.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi Eric,
On Tue, 24 Jan 2023 13:46:08 -0800 Eric Biggers <ebiggers@kernel.org> wrote:
>
> I've moved the fscrypt and fsverity development branches to split them up
> properly and make it clear what each branch is for. Therefore, can you please
> remove the following branches from linux-next:
>
> Repo: git://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git
> Branches: master, for-stable, and fsverity
>
> And please add the following branches to linux-next:
>
> Repo: https://git.kernel.org/pub/scm/fs/fscrypt/linux.git
> Branches: for-next and for-current
>
> Repo: https://git.kernel.org/pub/scm/fs/fsverity/linux.git
> Branches: for-next and for-current
>
> Also please ensure the contacts match the corresponding MAINTAINERS file
> entries. For fscrypt that is:
>
> M: Eric Biggers <ebiggers@kernel.org>
> M: Theodore Y. Ts'o <tytso@mit.edu>
> M: Jaegeuk Kim <jaegeuk@kernel.org>
>
> and for fsverity that is:
>
> M: Eric Biggers <ebiggers@kernel.org>
> M: Theodore Y. Ts'o <tytso@mit.edu>
All done. They will be included on Friday (as I am not doing a tree
tomorrow).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-01-25 4:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 21:46 Please update fscrypt and fsverity branches in linux-next Eric Biggers
2023-01-25 4:48 ` Stephen Rothwell [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=20230125154818.671047ae@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-next@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 read-only IMAP folder(s) and NNTP newsgroup(s).