From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] removal of /lib/unicode
Date: Tue, 28 Mar 2023 00:15:10 +0200 [thread overview]
Message-ID: <CAFSF3XMFn=nRky-0Qw2p04UDn2LiPH84c5U3-MQumL+2PZdkcQ@mail.gmail.com> (raw)
In-Reply-To: <4e26cf8611ab115f@orthanc.ca>
you people with your own customized branches: i hope you're sharing
your divergences, it might be helpful to others, educational, or at
least curious to some people here.
On 3/27/23, Lyndon Nerenberg (VE7TFX/VE6BBM) <lyndon@orthanc.ca> wrote:
> Michael Misch writes:
>
>> People in 9front clearly want to use this to meet their computing needs.
>> =
>> It can=E2=80=99t also exist as a higher definition of truth or purity, =
>
> The nice thing about having all the source in git is that you can
> create your own local branch and then cherry pick the changes you
> want to adopt. While these days I mostly run 9front, there are
> parts of it that I disagree with, or where I want or need to do
> things differently. Git branches makes that a breeze.
>
> So if you want back /lib/unicode, or anything else, create a branch,
> revert the change, rebuild, and you're done.
>
> Plan9 was never meant to be "one size fits all." It's a base for
> extension and customization.
>
> And never forget namespaces. Don't like something? Map over it!
>
> --lyndon
>
next prev parent reply other threads:[~2023-03-27 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 2:23 sl
2023-03-26 2:33 ` [9front] " Anthony Martin
2023-03-26 2:55 ` Jacob Moody
2023-03-26 3:05 ` sl
2023-03-26 3:25 ` Jacob Moody
2023-03-26 3:08 ` sl
2023-03-26 3:09 ` Sigrid Solveig Haflínudóttir
2023-03-26 4:37 ` Kurt H Maier
2023-03-26 13:26 ` qwx
2023-03-26 14:27 ` ori
2023-03-26 17:43 ` Jacob Moody
2023-03-26 14:52 ` cinap_lenrek
2023-03-26 19:27 ` hiro
2023-03-26 19:42 ` [9front] " Michael Misch
2023-03-26 20:46 ` hiro
2023-03-26 23:24 ` Kurt H Maier
2023-03-27 21:40 ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2023-03-27 22:15 ` hiro [this message]
2023-03-28 0:01 ` Sigrid Solveig Haflínudóttir
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='CAFSF3XMFn=nRky-0Qw2p04UDn2LiPH84c5U3-MQumL+2PZdkcQ@mail.gmail.com' \
--to=23hiro@gmail.com \
--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).