diff mbox

MAINTAINERS: fscrypt: update mailing list, patchwork, and git

Message ID 20170426234300.54741-1-ebiggers3@gmail.com
State Not Applicable, archived
Headers show

Commit Message

Eric Biggers April 26, 2017, 11:43 p.m. UTC
From: Eric Biggers <ebiggers@google.com>

Now that there has been a dedicated mailing list, patchwork project, and
git repository set up for filesystem encryption, update the MAINTAINERS
file accordingly.

Signed-off-by: Eric Biggers <ebiggers@google.com>
---
 MAINTAINERS | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

Comments

Richard Weinberger April 27, 2017, 7:37 a.m. UTC | #1
Eric,

On Thu, Apr 27, 2017 at 1:43 AM, Eric Biggers <ebiggers3@gmail.com> wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> Now that there has been a dedicated mailing list, patchwork project, and
> git repository set up for filesystem encryption, update the MAINTAINERS
> file accordingly.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  MAINTAINERS | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 38d3e4ed7208..22b509fb1c5e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5365,10 +5365,12 @@ F:      Documentation/filesystems/caching/
>  F:     fs/fscache/
>  F:     include/linux/fscache*.h
>
> -FS-CRYPTO: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
> +FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
>  M:     Theodore Y. Ts'o <tytso@mit.edu>
>  M:     Jaegeuk Kim <jaegeuk@kernel.org>

IMHO we should also add such an entry, to match reality:

R:      Eric Biggers <ebiggers@google.com>
Eric Biggers April 27, 2017, 5:45 p.m. UTC | #2
On Thu, Apr 27, 2017 at 09:37:18AM +0200, Richard Weinberger wrote:
> > +FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
> >  M:     Theodore Y. Ts'o <tytso@mit.edu>
> >  M:     Jaegeuk Kim <jaegeuk@kernel.org>
> 
> IMHO we should also add such an entry, to match reality:
> 
> R:      Eric Biggers <ebiggers@google.com>
> 

Well, we could, but IMO it's a little pointless since there's now a dedicated
mailing list, so there's no need to Cc me separately from the list.  I think
explicitly listing reviewer(s) is more useful for subsystems that don't have a
dedicated mailing list.

Eric
Richard Weinberger April 27, 2017, 7:12 p.m. UTC | #3
Eric,

Am 27.04.2017 um 19:45 schrieb Eric Biggers:
> On Thu, Apr 27, 2017 at 09:37:18AM +0200, Richard Weinberger wrote:
>>> +FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
>>>  M:     Theodore Y. Ts'o <tytso@mit.edu>
>>>  M:     Jaegeuk Kim <jaegeuk@kernel.org>
>>
>> IMHO we should also add such an entry, to match reality:
>>
>> R:      Eric Biggers <ebiggers@google.com>
>>
> 
> Well, we could, but IMO it's a little pointless since there's now a dedicated
> mailing list, so there's no need to Cc me separately from the list.  I think
> explicitly listing reviewer(s) is more useful for subsystems that don't have a
> dedicated mailing list.

It depends on your workflow.
i.e. my mail filters give mails that go directly to me a much higher priority.

Thanks,
//richard
Amir Goldstein April 28, 2017, 5:47 a.m. UTC | #4
On Thu, Apr 27, 2017 at 8:45 PM, Eric Biggers <ebiggers3@gmail.com> wrote:
> On Thu, Apr 27, 2017 at 09:37:18AM +0200, Richard Weinberger wrote:
>> > +FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
>> >  M:     Theodore Y. Ts'o <tytso@mit.edu>
>> >  M:     Jaegeuk Kim <jaegeuk@kernel.org>
>>
>> IMHO we should also add such an entry, to match reality:
>>
>> R:      Eric Biggers <ebiggers@google.com>
>>
>
> Well, we could, but IMO it's a little pointless since there's now a dedicated
> mailing list, so there's no need to Cc me separately from the list.  I think
> explicitly listing reviewer(s) is more useful for subsystems that don't have a
> dedicated mailing list.
>

Does the fscrypt mailing list allow posting for non-subscribers?
It is often a nuisance for a passing by developer to subscribe to a mailing list
just to report a bug or CC a relevant patch.
Theodore Ts'o April 30, 2017, 6:23 a.m. UTC | #5
On Fri, Apr 28, 2017 at 08:47:41AM +0300, Amir Goldstein wrote:
> 
> Does the fscrypt mailing list allow posting for non-subscribers?
> It is often a nuisance for a passing by developer to subscribe to a mailing list
> just to report a bug or CC a relevant patch.

As far as I know, all of the vger.kernel.org lists allow
non-subscribers to post.

       	   		   	       		       - Ted
Theodore Ts'o April 30, 2017, 6:24 a.m. UTC | #6
On Wed, Apr 26, 2017 at 04:43:00PM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Now that there has been a dedicated mailing list, patchwork project, and
> git repository set up for filesystem encryption, update the MAINTAINERS
> file accordingly.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>

Thanks, applied.

					- Ted
diff mbox

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index 38d3e4ed7208..22b509fb1c5e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -5365,10 +5365,12 @@  F:	Documentation/filesystems/caching/
 F:	fs/fscache/
 F:	include/linux/fscache*.h
 
-FS-CRYPTO: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
+FSCRYPT: FILE SYSTEM LEVEL ENCRYPTION SUPPORT
 M:	Theodore Y. Ts'o <tytso@mit.edu>
 M:	Jaegeuk Kim <jaegeuk@kernel.org>
-L:	linux-fsdevel@vger.kernel.org
+L:	linux-fscrypt@vger.kernel.org
+Q:	https://patchwork.kernel.org/project/linux-fscrypt/list/
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git
 S:	Supported
 F:	fs/crypto/
 F:	include/linux/fscrypt*.h