From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [Flent-users] [tohojo/flent] Release v2.0.1 - Flent v2.0.1
Date: Thu, 24 Jun 2021 15:03:40 -0700 [thread overview]
Message-ID: <tohojo/flent/releases/45201674@github.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
Released on 2021-06-24.
Changes since v2.0.0 include:
- Fix globbing in plot and test definitions so it works on newer Python
versions
- Don't hang forever while trying to process invalid time series data, and
check fping timestamp output before using it (fixes a hang bug when using
certain versions of fping on BSD and OSX)
- Don't crash on metadata collection if hexdump is not available on the system.
- Clarify that the Flent license doesn't apply to its output
--
You are receiving this because you are subscribed to this thread.
View it on GitHub:
https://github.com/tohojo/flent/releases/tag/v2.0.1
[-- Attachment #2: Type: text/html, Size: 2517 bytes --]
reply other threads:[~2021-06-24 22:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tohojo/flent/releases/45201674@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=noreply@github.com \
--cc=subscribed@noreply.github.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