Update minimum supported TLS version to 1.2.

[notdurson]

No description provided.

[rg0now]

Thanks, looks reasonable.

Can we get away without a code-owners file, is it some sort of a requirement on your side? We will ask you to collapse your patches into a single commit so that we can merge clearly, i.e., your identity will be there forever in the git tree, isn't that enough?

[notdurson]

Yes sorry, I will remove the codeowners file (it was intended for our internal fork).

…

On Wed, Dec 4, 2024, 04:02 Gabor Retvari ***@***.***> wrote: Thanks, looks reasonable. Can we get away without a code-owners file, is it some sort of a requirement on your side? We will ask you to collapse your patches into a single commit so that we can merge clearly, i.e., your identity will be there forever in the git tree, isn't that enough? — Reply to this email directly, view it on GitHub <#182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM27UK2CHLLIH4YXJA7P43T2D3AITAVCNFSM6AAAAABS6GMFSGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGYYTGNBSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[notdurson]

@rg0now deleted. Can you check again pls?

[rg0now]

Very nice, thanks. Last request: can you collapse the whole thing into a single commit? I think if I squash-merge you lose your authorship (is that true?), but if I merge as is we mess up the git history with lots of useless commits. Wdyt?

[notdurson]

Gabor, I can - I'm going to open a new PR though, because my local commit log is messed up.