From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: new release?
Date: Wed, 25 Feb 2004 13:22:50 -0700 [thread overview]
Message-ID: <aa1efcfff17955e9ac10fa6afe786c97@plan9.ucalgary.ca> (raw)
In-Reply-To: <200402252054.i1PKsxi6088476@adat.davidashen.net>
the way i see it:
"not really alive, not completely dead yet" describes it reasonably
well. the version numbers won't change because updating via the
replica at sources.cs.bell-labs takes care of daily patches and
trivial updates. it has the ability to take care of major updates
too, so perhaps there will never be a next plan9 release (think flow
vs discrete events).
the only time i heard 'R5' mentioned was to commemorate the switch to
fossil + the OSI-approved license, and to reorganize the tree so that
things brought in under a different license (ghostscript) are clearly
visible outside of the main Plan 9 tree (at least that's what i
understood from the directory tree on sources.cs).
sweeping changes in Plan 9 happen very rarely in my opinion (R3,
venti+fossil and 9P2000 were the ones that have happen in my lifetime
as a 9fan). to add to what ron said, people have mentioned on the
list running binaries from 1995 without problems on the latest p9
installations...
andrey
next prev parent reply other threads:[~2004-02-25 20:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 20:49 Noah Evans
2004-02-25 20:54 ` David Tolpin
2004-02-25 20:22 ` andrey mirtchovski [this message]
2004-02-25 21:33 ` dbailey27
2004-02-26 6:20 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 21:18 Noah Evans
2004-02-25 21:27 ` ron minnich
2004-02-25 22:56 ` Charles Forsyth
2004-02-26 0:17 ` Taj Khattra
2004-02-26 6:23 ` boyd, rounin
2004-02-25 20:44 chris niewiarowski
2004-02-25 18:31 chris niewiarowski
2004-02-25 18:59 ` matt
2004-02-26 6:09 ` boyd, rounin
2004-02-25 20:34 ` ron minnich
2004-02-25 20:43 ` David Tolpin
2004-02-25 20:53 ` ron minnich
2004-02-25 20:59 ` David Tolpin
2004-02-25 21:10 ` Christopher Nielsen
2004-02-25 21:13 ` David Tolpin
2004-02-25 21:45 ` Christopher Nielsen
2004-02-25 21:55 ` David Tolpin
2004-02-25 22:39 ` ron minnich
2004-02-26 4:36 ` Christopher Nielsen
2004-02-25 22:41 ` 9nut
2004-02-25 22:47 ` David Tolpin
2004-02-25 23:03 ` David Presotto
2004-02-25 23:50 ` Geoff Collyer
2004-02-26 1:36 ` Derek Fawcus
2004-02-26 1:44 ` David Presotto
2004-02-26 3:49 ` Geoff Collyer
2004-02-25 23:29 ` Dave Lukes
2004-02-25 23:59 ` 9nut
2004-02-25 21:25 ` David Presotto
2004-02-26 0:56 ` Brantley Coile
2004-02-25 21:35 ` matt
2004-02-25 22:39 ` 9nut
2004-02-25 22:00 ` Scott Schwartz
2004-02-25 22:05 ` David Tolpin
2004-02-25 22:39 ` Scott Schwartz
2004-02-26 6:26 ` boyd, rounin
2004-02-26 18:48 ` rog
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=aa1efcfff17955e9ac10fa6afe786c97@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/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).