Wilfred Mallawa commented on a discussion: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1989#note_2668528934


Thanks for the feedback! I have renamed the function as you suggested.

To your second point, it is not essential that we know if it was the 
`record_size_limit` extension, but just the maximum send size to obey that the 
kernel will need to adhere to. So I think for now we can get away with just 
getting the send size.

-- 
Reply to this email directly or view it on GitLab: 
https://gitlab.com/gnutls/gnutls/-/merge_requests/1989#note_2668528934
You're receiving this email because of your account on gitlab.com.


_______________________________________________
Gnutls-devel mailing list
Gnutls-devel@lists.gnutls.org
http://lists.gnupg.org/mailman/listinfo/gnutls-devel
  • [gnutls-de... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities
    • Re: [... Read-only notification of GnuTLS library development activities

Reply via email to