9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Very old bug in db(1)
Date: Thu, 19 Mar 2015 10:12:32 +0100	[thread overview]
Message-ID: <CAHL7psFuGQtitsxp7fdKE-xrc0aeuMAAPpEryf=KdsoDV36_zg@mail.gmail.com> (raw)
In-Reply-To: <56fdc9351a20a3af81daac04322109f4@proxima.alt.za>

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

Oh, I completely missed patch(1). And actually it was just when one should
look up for at first... man pages. Sorry.

Thanks for the tip!

It's a fragmented small community and that is just sad.  It is not
> likely that things will get better in the foreseeable future, so pick
> your side :-)


To pick a side, one should knows the "contenders" enough. :-)
It's very hard to find clear statements about the differences between the
various plan9 flavours, or clear descriptions of the vision driving the
development of each fork (at least I wasn't able to find them).
This is particularly true for plan9 forks that bet on Plan9 evolution
outside bell labs (9atom and 9front), while it's easy to get the
differences between 9legacy, Inferno, Nix-os etc...

More than 15 years ago, when I started using linux, it was easy to see how
Debian was different from RedHat or Suse.
In the Plan9 ecosystem, while looks that some are quite upsets about such
differences, it's hard to grasp them from the outside.


Giacomo

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

  reply	other threads:[~2015-03-19  9:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  6:41 Roberto E. Vargas Caballero
2015-03-19  8:01 ` Giacomo Tesio
2015-03-19  8:41   ` lucio
2015-03-19  9:12     ` Giacomo Tesio [this message]
2015-03-19 10:12       ` lucio
2015-03-19 10:47   ` cinap_lenrek

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='CAHL7psFuGQtitsxp7fdKE-xrc0aeuMAAPpEryf=KdsoDV36_zg@mail.gmail.com' \
    --to=giacomo@tesio.it \
    --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).