From: sml@firstpost.pub
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Difference between Plan 9 legacy and 9front
Date: Thu, 27 Jan 2022 07:34:44 -0500 [thread overview]
Message-ID: <16432868840.6D279.53677@composer.9fans.topicbox.com> (raw)
In-Reply-To: <717FEE89-B28E-4AFD-81DF-18362E1B12B2@babicovi.cz>
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Thank you so much for your detailed and helpful reply. So far I've found some informative (if a bit older) sites on 9legacy and 9front, but your explanation really helps me classify the two approaches.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tbaab87532a204e00-M6b486ab261a37886dfbf486b
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 932 bytes --]
next prev parent reply other threads:[~2022-01-27 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 11:12 sml
2022-01-27 11:45 ` Alexandr Babic
2022-01-27 12:34 ` sml [this message]
2022-01-27 12:18 ` Keith Gibbs
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=16432868840.6D279.53677@composer.9fans.topicbox.com \
--to=sml@firstpost.pub \
--cc=9fans@9fans.net \
/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).