public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Eric Biggers <ebiggers@kernel•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Cc: "Theodore Y. Ts'o" <tytso@mit•edu>,
	Jaegeuk Kim <jaegeuk@kernel•org>,
	linux-fscrypt@vger•kernel.org, fsverity@lists•linux.dev
Subject: Please update fscrypt and fsverity branches in linux-next
Date: Tue, 24 Jan 2023 13:46:08 -0800	[thread overview]
Message-ID: <Y9BRoE/SIg1aUh+P@sol.localdomain> (raw)

Hi Stephen,

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>

Thanks!

- Eric

next             reply	other threads:[~2023-01-24 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 21:46 Eric Biggers [this message]
2023-01-25  4:48 ` Please update fscrypt and fsverity branches in linux-next Stephen Rothwell

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=Y9BRoE/SIg1aUh+P@sol.localdomain \
    --to=ebiggers@kernel$(echo .)org \
    --cc=fsverity@lists$(echo .)linux.dev \
    --cc=jaegeuk@kernel$(echo .)org \
    --cc=linux-fscrypt@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tytso@mit$(echo .)edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox