From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Very old bug in db(1)
Date: Thu, 19 Mar 2015 12:12:59 +0200 [thread overview]
Message-ID: <bb0571588e3012a15013e55fe6a1b9a6@proxima.alt.za> (raw)
In-Reply-To: <CAHL7psFuGQtitsxp7fdKE-xrc0aeuMAAPpEryf=KdsoDV36_zg@mail.gmail.com>
> 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).
I suspect a lot went on in IRC because I've been around this mailing
list for decades and I missed most of that aspect. The best person to
consult with is David de Colombier, if his web site is not the
reference, it ought to be. He'll pop up sooner or later.
Lucio/
next prev parent reply other threads:[~2015-03-19 10: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
2015-03-19 10:12 ` lucio [this message]
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=bb0571588e3012a15013e55fe6a1b9a6@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).