From: Theodore Ts'o <tytso@mit.edu>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, jaegeuk@kernel.org,
ebiggers@google.com, mhalcrow@google.com, richard@nod.at,
linux-ext4@vger.kernel.org, linux-f2fs@vger.kernel.org
Subject: Re: Creating a mailing list, git tree, and patchwork project for fscrypt
Date: Fri, 16 Dec 2016 17:04:19 -0500 [thread overview]
Message-ID: <20161216220419.znasf5wjkpb7qazr@thunk.org> (raw)
In-Reply-To: <20161216205330.GB14264@gmail.com>
On Fri, Dec 16, 2016 at 12:53:30PM -0800, Eric Biggers wrote:
> Sounds great!
>
> I guess it will be "fscrypt" and not "fscrypto"? There has been some confusion
> about which term to use but it seems to be settling on "fscrypt".
It was originally fscrypt, but then fscrypto crept in when we
refactored the out to the fs/crypto directory from fs/ext4. I was
planning on cleaning that up before we had too many file systems users
of fscrypt that we would need to synchronzie with, but it'll be easier
to do this as a separate git tree. We can either do it at the very
beginning of the merge window (and have all of the file systems pull
the change into fs/crypt), or I can work with Linus to do it right
after the next next merge window closes.
My preferences would be for the former, given where we are in the
development cycle.
Any objections?
- Ted
next prev parent reply other threads:[~2016-12-16 22:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 20:37 Creating a mailing list, git tree, and patchwork project for fscrypt Theodore Ts'o
2016-12-16 20:39 ` Richard Weinberger
2016-12-16 20:53 ` Eric Biggers
2016-12-16 22:04 ` Theodore Ts'o [this message]
2016-12-16 22:25 ` Eric Biggers
2017-03-29 21:14 ` Eric Biggers
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=20161216220419.znasf5wjkpb7qazr@thunk.org \
--to=tytso@mit.edu \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=richard@nod.at \
/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).