From: Richard Weinberger <richard@nod.at>
To: Michael Halcrow <mhalcrow@google.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
kzak@redhat.com, "Theodore Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Eric Biggers <ebiggers@google.com>,
David Gstir <david@sigma-star.at>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
linux-f2fs-devel@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFD] Common userspace tool for fscypto
Date: Tue, 29 Nov 2016 21:48:16 +0100 [thread overview]
Message-ID: <f9bc005b-4e25-d705-e091-5f930e4246b1@nod.at> (raw)
In-Reply-To: <CA+POJK10M3_GhP_Ge4qkQF4gSNMUXVr5kem9Ak4EDmVRvRUg7g@mail.gmail.com>
Michael,
On 19.10.2016 19:36, Michael Halcrow wrote:
>> That said, what about implementing such a tool as part of util-linux to control
>> fscrypto? We (David and I) would volunteer.
>
> While discussing several changes we have staged for release (we're
> trying to minimize churn by batching a large set of format changes all
> at once), we've recently recognized this need on my team and were
> planning on starting work on exactly what you propose.
Did this plan already materialize? :-)
Thanks,
//richard
next prev parent reply other threads:[~2016-11-29 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 11:35 [RFD] Common userspace tool for fscypto Richard Weinberger
2016-10-19 17:36 ` Michael Halcrow
2016-10-24 11:59 ` Richard Weinberger
2016-11-29 20:48 ` Richard Weinberger [this message]
2016-11-29 21:42 ` Joe Richey
2016-11-29 21:59 ` Richard Weinberger
2016-11-30 0:04 ` Eric Biggers
2016-11-30 8:27 ` Richard Weinberger
2016-12-03 0:40 ` Eric Biggers
2016-11-30 21:00 ` Theodore Ts'o
2016-10-24 12:49 ` Karel Zak
2016-10-24 13:28 ` 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=f9bc005b-4e25-d705-e091-5f930e4246b1@nod.at \
--to=richard@nod.at \
--cc=david@sigma-star.at \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=kzak@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--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).