public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
* Please update fscrypt and fsverity branches in linux-next
@ 2023-01-24 21:46 Eric Biggers
  2023-01-25  4:48 ` Stephen Rothwell
  0 siblings, 1 reply; 2+ messages in thread
From: Eric Biggers @ 2023-01-24 21:46 UTC (permalink / raw)
  To: Stephen Rothwell, linux-next
  Cc: Theodore Y. Ts'o, Jaegeuk Kim, linux-fscrypt, fsverity

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Please update fscrypt and fsverity branches in linux-next
  2023-01-24 21:46 Please update fscrypt and fsverity branches in linux-next Eric Biggers
@ 2023-01-25  4:48 ` Stephen Rothwell
  0 siblings, 0 replies; 2+ messages in thread
From: Stephen Rothwell @ 2023-01-25  4:48 UTC (permalink / raw)
  To: Eric Biggers
  Cc: linux-next, Theodore Y. Ts'o, Jaegeuk Kim, linux-fscrypt,
	fsverity

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-01-25  4:48 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-24 21:46 Please update fscrypt and fsverity branches in linux-next Eric Biggers
2023-01-25  4:48 ` Stephen Rothwell

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