This is the second time, that I'm aware of, that the wording of the CLA has
prevented a PR from being accepted.
While this won't help the first case I'm aware of, perhaps there needs to be an
exception/special-case in the CLA for code in RFCs, or other similar
publications, where the author is
Hi openssl-project:
Given the typical release cadence and the imminent demise of 1.1.0, will there
be another set bug fix releases (i.e. a final 1.1.0 release with friends)?
Thanks,
--
-Todd Short
// tsh...@akamai.com
// “One if by land, two if by sea, threeif by the Internet."
smime.p7s
Des
This type of API-braking change should be reserved for something like 3.0, not
a patch release.
Despite it being a "incorrect", it is expected behavior.
--
-Todd Short
// tsh...@akamai.com
// “One if by land, two if by sea, three if by the Internet."
> On Mar 26, 2020, at 11:03 AM, Dr. Matthias
As someone who is currently playing around with QUIC branches based on the tags
and branch names, I *always* screw things up while typing. I wouldn't mind if
the key were banned from tags and branch names.
--
-Todd Short
// tsh...@akamai.com
// “One if by land, two if by sea, three if by the Int
They also correspond directly to EVP_MAC and EVP_KDF types. Would the types
change as well?
--
-Todd Short
// tsh...@akamai.com
// “One if by land, two if by sea, three if by the Internet."
> On Jul 23, 2020, at 11:56 AM, Matt Caswell wrote:
>
>
>
> On 23/07/2020 16:52, Richard Levitte wrote: