From: Chuck Lever <chuck.lever@oracle.com>
To: kernel-tls-handshake <kernel-tls-handshake@lists.linux.dev>
Subject: Preparing for ktls-utils-1.0
Date: Wed, 29 Jan 2025 09:39:47 -0500 [thread overview]
Message-ID: <77ac012b-0ad7-4aa4-8b27-7a837c6c03be@oracle.com> (raw)
I received a request to publish a fresh release of ktls-utils.
My thought was this is an opportunity to release a 1.0.
I can request a Parfait run on the current source code. I've
never gotten Coverity to work. Any other analysis tools we
can try?
Are there any other features that should be in this release?
All code review (or re-review) is welcome.
--
Chuck Lever
next reply other threads:[~2025-01-29 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 14:39 Chuck Lever [this message]
2025-01-29 20:03 ` Preparing for ktls-utils-1.0 Chuck Lever
2025-02-06 16:41 ` Chuck Lever
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=77ac012b-0ad7-4aa4-8b27-7a837c6c03be@oracle.com \
--to=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.