9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Matt <matthpmoreira@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Despite being called a fork, is 9front similar to how Linux distros work?
Date: Mon, 17 Jan 2022 18:31:02 -0500	[thread overview]
Message-ID: <16424622620.b9EedC5.684450@composer.9fans.topicbox.com> (raw)
In-Reply-To: <16424615390.0F13B68C3.21800@composer.9fans.topicbox.com>

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

But that's why 9front was forked, right? They say it on their FAQ. Even though Plan 9 isn't being developed anymore, doesn't the fork cause worry that one day they become too different, especially since the community is rather centered around Plan 9 rather than 9front? Or is the community actively trying to make 9front be accepted as the official continuation of Plan 9?
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-M416d1bd55b012e3817746334
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 1106 bytes --]

  parent reply	other threads:[~2022-01-17 23:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 22:04 matthpmoreira
2022-01-17 22:41 ` Humm
2022-01-17 23:04 ` ori
2022-01-17 23:18   ` Matt
2022-01-17 23:22     ` ori
2022-01-17 23:31     ` Matt [this message]
2022-01-17 23:36       ` Sigrid Solveig Haflínudóttir
2022-01-18  0:29         ` Matt
2022-01-18  0:33           ` hiro
2022-01-18 16:22           ` Humm
2022-01-18 18:54             ` Antonio Barrones
2022-01-18 19:55               ` Humm
2022-01-18 20:48               ` Kurt H Maier via 9fans
2022-01-18 22:16               ` vic.thacker
2022-01-18 22:59                 ` Duke Normandin
2022-01-18  0:47         ` Kurt H Maier via 9fans
2022-01-18  4:38         ` Andrew Back
2022-01-18  0:20       ` Thaddeus Woskowiak

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=16424622620.b9EedC5.684450@composer.9fans.topicbox.com \
    --to=matthpmoreira@gmail.com \
    --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).