From: Romano <me+unobe@fallglow.com>
To: 9front@9front.org
Subject: Re: [9front] Re: rc: value component separators
Date: Fri, 12 Jul 2024 23:04:55 -0700 [thread overview]
Message-ID: <49BC9EA0E4CFC179E5FAB44FA9F1A02B@smtp.pobox.com> (raw)
In-Reply-To: <ZpG5C4eRhkJb8Sz_@alice>
Ah, ok, that makes sense now. Thanks, Anthony.
prev parent reply other threads:[~2024-07-13 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 21:58 [9front] " Romano
2024-07-12 23:15 ` [9front] " Anthony Martin
2024-07-13 6:04 ` Romano [this message]
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=49BC9EA0E4CFC179E5FAB44FA9F1A02B@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).