From: Jared Henley <jared@henley.id.au>
To: 9front@9front.org
Subject: Re: [9front] How I Switched To Plan 9
Date: Wed, 4 Dec 2019 19:08:14 +1100 [thread overview]
Message-ID: <c4a1f198-3668-1f26-bb87-68bc5d291b81@henley.id.au> (raw)
In-Reply-To: <591D164ECE155454711BDE40E3B442A0@ewsd.inri.net>
On 4/12/19 3:06 pm, sl@stanleylieber.com wrote:
> http://helpful.cat-v.org/Blog/2019/12/03/0/
>
> sl
>
Little did I know that I would receive from you a long-form answer to my
earlier question. Many thanks.
Jared.
next parent reply other threads:[~2019-12-04 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <591D164ECE155454711BDE40E3B442A0@ewsd.inri.net>
2019-12-04 8:08 ` Jared Henley [this message]
[not found] <98478BC5748383C405BD06745D67D74F@ewsd.inri.net>
2019-12-04 4:37 ` Mark van Atten
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=c4a1f198-3668-1f26-bb87-68bc5d291b81@henley.id.au \
--to=jared@henley.id.au \
--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).