From: fulton@fulton.software
To: 9front@9front.org
Subject: Re: [9front] [PATCH] sha3 but fixed the code style
Date: Tue, 01 Jun 2021 08:09:18 -0700 [thread overview]
Message-ID: <68C2D709B94513F227A4C2B56EDF6FF9@fulton.software> (raw)
In-Reply-To: <1C4DE32C373501A487F0F5F1AD185B49@felloff.net>
Quoth cinap_lenrek@felloff.net:
> i do not like b[200] aliasing bstate here. i think it would be better to
> handle this explicitely in the code.
Why?
--
Fulton fulton.software!fulton
next prev parent reply other threads:[~2021-06-01 17:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 16:00 fulton
2021-06-01 12:46 ` cinap_lenrek
2021-06-01 15:09 ` fulton [this message]
2021-06-02 12:16 ` cinap_lenrek
2021-06-01 19:51 ` fulton
2021-06-02 12:15 ` cinap_lenrek
2021-06-02 13:46 ` kemal
2021-06-02 14:16 ` kemal
2021-06-03 1:30 ` ori
2021-06-03 16:56 ` fulton
2021-06-02 14:45 ` cinap_lenrek
2021-06-03 15:24 ` fulton
2021-06-02 21:04 ` fulton
2021-06-03 20:28 ` hiro
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=68C2D709B94513F227A4C2B56EDF6FF9@fulton.software \
--to=fulton@fulton.software \
--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).