From: Romano <me+unobe@fallglow.com>
To: 9front@9front.org
Subject: Re: [9front] ramfs usage
Date: Tue, 18 Jun 2024 10:59:04 -0700 [thread overview]
Message-ID: <14D64F8DE98193582F542196E9717C70@smtp.pobox.com> (raw)
In-Reply-To: <E87921D07364B0CC69AAD145361B45D3@smtp.pobox.com>
Ping. Here's a cleaned up patch:
http://okturing.com/src/20102/body
next prev parent reply other threads:[~2024-06-18 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 22:03 me+unobe
2024-05-16 22:19 ` Romano
2024-06-18 17:59 ` Romano [this message]
2024-06-19 20:36 ` ori
2024-06-19 21:21 ` Jacob Moody
2024-06-20 4:43 ` Romano
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=14D64F8DE98193582F542196E9717C70@smtp.pobox.com \
--to=me+unobe@fallglow.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).