From: Joshua Lock <joshua.g.lock at linux.intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-tools 3.1.0 release candidate
Date: Thu, 21 Jun 2018 22:09:50 +0100 [thread overview]
Message-ID: <999d2b37-5230-60d0-a992-71c3b5d69835@linux.intel.com> (raw)
In-Reply-To: 56383db7-121b-cce1-7713-b1ff2ca94cb6@linux.intel.com
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On 11/06/2018 14:24, Joshua Lock wrote:
> Hello all,
>
> I've just tagged and signed rc0 for tpm2-tools 3.1.0. The main feature
> of this version of the tools is to port to tpm2-tss 2.0.
>
> Full details are in the CHANGELOG and available on the GitHub release page:
> https://github.com/tpm2-software/tpm2-tools/releases/tag/3.1.0-rc0
>
> Feedback on this rc is very much appreciated.
The RC window was very quiet, with no feedback received on the tools.
Now that the 2.0.0 release of the TSS has been made I've tagged, signed
and released the 3.0.1 version of the tools for use with them.
https://github.com/tpm2-software/tpm2-tools/releases/tag/3.1.0
Regards,
Joshua
next reply other threads:[~2018-06-21 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 21:09 Joshua Lock [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-11 13:24 [tpm2] tpm2-tools 3.1.0 release candidate Joshua Lock
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=999d2b37-5230-60d0-a992-71c3b5d69835@linux.intel.com \
--to=tpm2@lists.01.org \
/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