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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
