From: Philip Tricca <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] tpm2-abrmd 2.0 RCs
Date: Fri, 22 Jun 2018 08:43:20 -0700 [thread overview]
Message-ID: <20180622154320.GI2727@intel.com> (raw)
In-Reply-To: 20180607004124.GE2727@intel.com
[-- Attachment #1: Type: text/plain, Size: 817 bytes --]
On Wed, Jun 06, 2018 at 05:41:24PM -0700, Philip Tricca wrote:
> I've just taged and signed RC0 for tabrmd version 2.0.0. This release is
> compatible with the future version 2.0.0 of the tpm2-tss libraries and
> will be released soon after. The release process currently on going for
> tpm2-tss has been a bit protracted and so for the sake of time we're
> overlapping the RCs.
The tpm2-tss 2.0 release is now done and the RC process for the tabrmd
has been pretty quiet. Only one change was made during RC0 and this was
a one-line change removing an unnecessary '#include' directive. This
msall change isn't sufficient for another RC and so the tabrmd 2.0.0
release has just been tagged and artifacts uploaded here:
https://github.com/tpm2-software/tpm2-abrmd/releases/tag/2.0.0
Regards,
Philip
next reply other threads:[~2018-06-22 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 15:43 Philip Tricca [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-07 0:41 [tpm2] tpm2-abrmd 2.0 RCs Philip Tricca
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=20180622154320.GI2727@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