9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Bence Fábián" <begnoc@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] these are release of 9front?
Date: Tue,  8 Jan 2013 12:24:01 +0100	[thread overview]
Message-ID: <CAOCRf5W6QV-sWLMCkdoHaDwWkiDgWgeND9UvfG0NGP_6R50HLA@mail.gmail.com> (raw)
In-Reply-To: <042f5704bc7dbee05ba3fbd09e1a493d@hamnavoe.com>

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

Since there are a lot of code flow between 9front and 9atom (even sources,
however that's mostly one directional) I would argue that having the
forks even make things better. Erik and Cinap can experiment more
freely and all the changes are available for everyone. Even breaking
driver compatibility worth it, since the kernel is so small anyway. It is
fairly straightforward to change things. Plan9 is an excellent playground
as you put it. It's a good thing everyone can make their own.

-bence


2013/1/8 Richard Miller <9fans@hamnavoe.com>

> > many drivers needed a rewrite anyway (like usb audio) because they
> > where a total mess.
>
> There are plenty of things in Plan 9 still in need of improvement
> or even rewriting.  That's why it makes me sad to see our small
> community being made even smaller when some of the most skilled
> programmers direct their efforts into splintering off their own
> little playgrounds instead of helping to make Plan 9 better for
> everyone.
>
>
>

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

  parent reply	other threads:[~2013-01-08 11:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08  1:07 Francesco Cardi
2013-01-08  1:17 ` John Floren
2013-01-08  1:27 ` sl
2013-01-08  9:09 ` Richard Miller
2013-01-08  9:59   ` cinap_lenrek
2013-01-08 10:15     ` Richard Miller
2013-01-08 10:36       ` cinap_lenrek
2013-01-08 10:52         ` Richard Miller
2013-01-08 11:10           ` lucio
2013-01-08 11:24           ` Bence Fábián [this message]
2013-01-08 14:14             ` steve
2013-01-08 15:37               ` erik quanstrom
2013-01-08 13:48           ` sl
2013-01-08 16:22             ` Wes Kussmaul
2013-01-08 14:24           ` cinap_lenrek
2013-01-08 14:33           ` cinap_lenrek
2013-01-08 14:52             ` David Leimbach
2013-01-08 15:53             ` Nemo
2013-01-08 19:38               ` Richard Miller
2013-01-08 20:40                 ` mveety
2013-01-08 20:48                   ` erik quanstrom
2013-01-08 20:54                     ` Matthew Veety
2013-01-08 22:42                       ` Federico G. Benavento
2013-01-09  4:23                 ` cinap_lenrek
2013-01-12 13:48                   ` Richard Miller
2013-01-12 14:12                     ` erik quanstrom
2013-01-12 14:35                       ` Richard Miller
2013-01-12 14:47                         ` Richard Miller
2013-01-08 19:18           ` erik quanstrom

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=CAOCRf5W6QV-sWLMCkdoHaDwWkiDgWgeND9UvfG0NGP_6R50HLA@mail.gmail.com \
    --to=begnoc@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).