From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] truetypefs
Date: Sat, 31 Oct 2020 12:42:53 +0100 [thread overview]
Message-ID: <EE36C959B6458A41F4AF1B1D1616B5AD@felloff.net> (raw)
In-Reply-To: <012440E4E4FD8FD9B1E1955DA8640092@sdf.org>
thanks!
it looks fine to me.
i forwarded the patch to the original author... she's the
expert on this and might explain why that assert was there.
--
cinap
next prev parent reply other threads:[~2020-10-31 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 17:45 truetypefs nicolagi
2020-10-31 11:42 ` cinap_lenrek [this message]
2020-11-06 16:07 ` [9front] truetypefs ori
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=EE36C959B6458A41F4AF1B1D1616B5AD@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).