From: ori@eigenstate.org
To: 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:04:21 -0500 [thread overview]
Message-ID: <C2CF20C234D9A2285387F6286CEEFD33@eigenstate.org> (raw)
In-Reply-To: <16424570840.4902C04.457895@composer.9fans.topicbox.com>
Quoth matthpmoreira@gmail.com:
> I know it's subjective, but a fork implies to me that the goals and
> methods of the forking developers are different from the original
> software, maybe eventually leading to a completely contrasted
> software, with different environment, tools and inner workings, like
> Android is to Linux. That's why I wanted to clarify this question.
More commonly, forks remain similar.
Xorg vs xfree86.
Libreoffice vs Openoffice
Mariadb vs MySQL
OpenBSD vs NetBSD
Blink vs Webkit
libav vs ffmpeg
etc, etc.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T395156d4f2b00cde-M23e31f49e85f7588f6b4c52e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2022-01-17 23:04 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 [this message]
2022-01-17 23:18 ` Matt
2022-01-17 23:22 ` ori
2022-01-17 23:31 ` Matt
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=C2CF20C234D9A2285387F6286CEEFD33@eigenstate.org \
--to=ori@eigenstate.org \
--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).