From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] libsec: fix bugs in tls extension handling
Date: Mon, 18 Oct 2021 18:22:10 +0200 [thread overview]
Message-ID: <0B9FE625686FC89AEC8300AA45F80876@felloff.net> (raw)
In-Reply-To: <CABO6shc=xG4m5YdUxZVf0VwLhZxnDeNYYxn5oNoRWxg-ehMQog@mail.gmail.com>
> about why i put n twice to the realloc size, well i think i did that
> accidentally. "2+2+1+n" should be "2+2+1+1".
makes sense.
--
cinap
next prev parent reply other threads:[~2021-10-19 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 17:38 kemal
2021-10-17 23:15 ` cinap_lenrek
2021-10-18 12:36 ` kemal
2021-10-18 16:22 ` cinap_lenrek [this message]
2021-10-17 23:36 ` cinap_lenrek
2021-10-17 23:46 ` cinap_lenrek
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=0B9FE625686FC89AEC8300AA45F80876@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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;
as well as URLs for NNTP newsgroup(s).