From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: [9front] So long, and thanks for all the fish!
Date: Mon, 30 Nov 2020 19:01:16 +0000 [thread overview]
Message-ID: <4ce65a4e-7320-4702-9e20-f8ad65e3948b@www.fastmail.com> (raw)
So sad that it should come to this. We thought most of you were... Okay, NO! That's enough of that.
I'm glad to see 9front getting some more interest in a good way, but for me, the increasing traffic on this list makes it the very worst kind of noise: _interesting_ noise. ;) I no longer use 9front or any other variant of Plan 9 because it's not the ideal system for me as I've described elsewhere. (Primarily, I was always struggling with one or other language. It's just my brain, I guess.) I hope you all keep having fun with the system, but it makes no sense for me to stay on the list. Peace out!
reply other threads:[~2020-11-30 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4ce65a4e-7320-4702-9e20-f8ad65e3948b@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).