From: Philip Silva <philip.silva@protonmail.com>
To: 9front@9front.org
Subject: Re: [9front] Go on ARM64
Date: Wed, 28 Dec 2022 21:43:03 +0000 [thread overview]
Message-ID: <9t5iga_ykP_vmR_vuFlag7_Gwk8tftEcFYis_hZrOyJKCs00EWYyQ7H-fwNhAZ27RvrZ0t9Usr5SeANerji4Qbqg9hn9rPolnN8Wr7C6FCs=@protonmail.com> (raw)
In-Reply-To: <F03F4B3673BBDECBF7B7D9C0C565C09F@eigenstate.org>
> Granted it's a bit dusty, but perhaps you can brush it off and cash it in. If you can't, we can probably
strike it from the FQA bounty list.
That would be something!
> next step -- let's get it upstream.
Definitely, there are (at least) 2 lines of debugging left-over and I need to check the tests, but I can create a PR then in the next days
next prev parent reply other threads:[~2022-12-28 21:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 17:29 Philip Silva
2022-12-28 17:51 ` Jacob Moody
2022-12-28 17:58 ` ori
2022-12-28 21:43 ` Philip Silva [this message]
2022-12-30 4:59 ` Fazlul Shahriar
2022-12-31 0:44 ` Philip Silva
2022-12-31 1:53 ` Fazlul Shahriar
2022-12-31 2:42 ` ori
2023-01-01 18:06 ` Philip Silva
2022-12-31 2:49 ` william
2022-12-31 4:04 ` Aaron Bieber
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='9t5iga_ykP_vmR_vuFlag7_Gwk8tftEcFYis_hZrOyJKCs00EWYyQ7H-fwNhAZ27RvrZ0t9Usr5SeANerji4Qbqg9hn9rPolnN8Wr7C6FCs=@protonmail.com' \
--to=philip.silva@protonmail.com \
--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).