From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fscrypt@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Eric Biggers <ebiggers@google.com>,
linux-f2fs-devel@lists.sourceforge.net,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Jaegeuk Kim <jaegeuk@kernel.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: fscrypt: update mailing list, patchwork, and git
Date: Thu, 27 Apr 2017 21:12:40 +0200 [thread overview]
Message-ID: <c980efed-3bd2-36f5-5564-060513f48e6c@nod.at> (raw)
In-Reply-To: <20170427174557.GB8130@gmail.com>
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
next prev parent reply other threads:[~2017-04-27 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 23:43 [PATCH] MAINTAINERS: fscrypt: update mailing list, patchwork, and git Eric Biggers
2017-04-27 7:37 ` Richard Weinberger
2017-04-27 17:45 ` Eric Biggers
2017-04-27 19:12 ` Richard Weinberger [this message]
2017-04-28 5:47 ` Amir Goldstein
2017-04-30 6:23 ` Theodore Ts'o
2017-04-30 6:24 ` Theodore Ts'o
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=c980efed-3bd2-36f5-5564-060513f48e6c@nod.at \
--to=richard@nod.at \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@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 \
--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 NNTP newsgroup(s).