From: Peter Hull <peterhull90@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GPLv2
Date: Thu, 13 Feb 2014 21:00:49 +0000 [thread overview]
Message-ID: <72D1680B-DAEA-41C4-B431-10C1659589A6@gmail.com> (raw)
In-Reply-To: <CAOFTvPJx4heChtR-0FHEr3ETovD9+JxnU8L+rfY_0Pw=t6Cv7g@mail.gmail.com>
There is a big discussion on this over at Hacker News which I don’t really understand but I think the main point was that this isn’t as big a change as it seems.
On the other hand, I’ve never heard of akaros. How similar is it to Plan9?
Pete
On 13 Feb 2014, at 20:53, Sergey Zhilkin <szhilkin@gmail.com> wrote:
> http://akaros.cs.berkeley.edu/files/Plan9License
>
> Hmmmm ......
>
> --
> С наилучшими пожеланиями
> Жилкин Сергей
> With best regards
> Zhilkin Sergey
next prev parent reply other threads:[~2014-02-13 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 20:53 Sergey Zhilkin
2014-02-13 21:00 ` Peter Hull [this message]
2014-02-13 21:18 ` Sergey Zhilkin
2014-02-13 23:28 ` Aram Hăvărneanu
2014-02-14 4:21 ` Oleg
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=72D1680B-DAEA-41C4-B431-10C1659589A6@gmail.com \
--to=peterhull90@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).