9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: elliott Elliott.Hughes@genedata.com
Subject: Keepers of the flame (was Re: [9fans] Re: etherelnk3.c)
Date: Mon, 15 Dec 1997 12:21:57 +0100	[thread overview]
Message-ID: <19971215112157.-VeqYTn6VUtyOBERyOQJYR79rYzksf1C23MD2UQFUUg@z> (raw)

G. David Butler wrote:
> Are we ready to build a team to do Plan9 enhancement/development?
> We could use the FreeBSD model.  Or do we want to leave the
> system as it is with Lucent as keeper of the updates?

Is Lucent really keeper of the updates anyway? It seems to me that every
time a problem is mentioned someone (often forsyth) says "oh yeah, I
fixed that ages ago; I'll look out the patch". I don't think it's true
that when I finally get me, my CD and sufficient computers all together
and all in the same country, I'll be able to pop over to Lucent and ftp
all the patches I need.

I'm not sure what you mean by the FreeBSD model. To me that means "stick
the source tree on an FTP site and let all and sundry play". That
doesn't seem to fit with the idea of us all having handed over cash to
AT&T and (presumably, I haven't read it yet) having agreed not to pass
anything on.

It certainly would be nice if we could guarantee that people don't have
to keep fixing things independently of one another. It might be
interesting to know what everyone's doing with Plan 9, too. Where
people's interests lie.

-- 
Elliott Hughes - GeneData AG, Postfach 254, CH-4016 Basel, Switzerland
mailto:elliott.hughes@genedata.com  http://users.ch.genedata.com/~enh/




             reply	other threads:[~1997-12-15 11:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-15 11:21 elliott [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-12-15 10:43 forsyth

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=19971215112157.-VeqYTn6VUtyOBERyOQJYR79rYzksf1C23MD2UQFUUg@z \
    --to=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).