From: Luca Boccassi <Luca.Boccassi@microsoft.com>
To: "ebiggers@kernel.org" <ebiggers@kernel.org>,
"linux-fscrypt@vger.kernel.org" <linux-fscrypt@vger.kernel.org>
Cc: "victorhsieh@google.com" <victorhsieh@google.com>,
"Jes.Sorensen@gmail.com" <Jes.Sorensen@gmail.com>,
"maco@android.com" <maco@android.com>,
"paullawrence@google.com" <paullawrence@google.com>
Subject: Re: [fsverity-utils PATCH 2/2] Rename "file measurement" to "file digest"
Date: Mon, 16 Nov 2020 11:27:52 +0000 [thread overview]
Message-ID: <89d2fb66e12663f685286f7db58cf1c3e41134ff.camel@microsoft.com> (raw)
In-Reply-To: <20201113213314.73616-3-ebiggers@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 795 bytes --]
On Fri, 2020-11-13 at 13:33 -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> As was done in the kernel, rename "file measurement" to "file digest".
> "File digest" has ended up being the more intuitive name, and it avoids
> using multiple names for the same thing.
>
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> NEWS.md | 6 +++---
> README.md | 20 ++++++++++----------
> include/libfsverity.h | 18 +++++++++---------
> programs/cmd_digest.c | 2 +-
> programs/cmd_measure.c | 2 +-
> programs/cmd_sign.c | 2 +-
> programs/fsverity.c | 4 ++--
> 7 files changed, 27 insertions(+), 27 deletions(-)
Acked-by: Luca Boccassi <luca.boccassi@microsoft.com>
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-11-16 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 21:33 [fsverity-utils PATCH 0/2] fsverity-utils cleanups Eric Biggers
2020-11-13 21:33 ` [fsverity-utils PATCH 1/2] Upgrade to latest fsverity_uapi.h Eric Biggers
2020-11-16 11:27 ` Luca Boccassi
2020-11-13 21:33 ` [fsverity-utils PATCH 2/2] Rename "file measurement" to "file digest" Eric Biggers
2020-11-16 11:27 ` Luca Boccassi [this message]
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=89d2fb66e12663f685286f7db58cf1c3e41134ff.camel@microsoft.com \
--to=luca.boccassi@microsoft.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=maco@android.com \
--cc=paullawrence@google.com \
--cc=victorhsieh@google.com \
/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