From: Richard Wolff rwolff@noao.edu
Subject: errata
Date: Thu, 17 Aug 1995 19:06:27 -0400 [thread overview]
Message-ID: <19950817230627.4U6nmcRXf8N3IzonJTdl7GFWy5EJLEGqZWsuj0UxgeM@z> (raw)
I'm curious as to how errata are going to be handled over the long
run. The posting via the web page is currently acceptable, but I'm not
convinced this will scale well. Moreover, there are various patches
being posted that may apparently cure a problem but, for some reason or
another, not be a solution that's adequately blessed by the plan9
developers: eg, they just don't like the solution, it doesn't fit the
long range notion of some changes they've not yet promulgated, it's
really not correct, etc. So I'll probably not want to incorporate
everything I see on the net ( :-) ). On the other hand, I don't want
to keep running a system with known and readily repaired bug(lets).
I'd like to be able to know what's the current "vanilla" plan9...that
is, the system that would be distributed today on a new CD-ROM, were
one to be generated. So, how are changes to be dealt with? Is there
going to be a clearinghouse for these? If the web page is used, should
one just expect to download it every so often and diff it against a
previous version to see what's changed? Or an ftp'able file that
contains all the diff listings suitable for something ala patch.
Richard
next reply other threads:[~1995-08-17 23:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-17 23:06 Richard [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-18 18:42 errata Scott
1995-07-31 5:51 errata Jeremy
1995-07-28 19:29 errata Scott
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=19950817230627.4U6nmcRXf8N3IzonJTdl7GFWy5EJLEGqZWsuj0UxgeM@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).