From: Scott Schwartz schwartz@galapagos.cse.psu.edu
Subject: errata
Date: Fri, 18 Aug 1995 14:42:23 -0400 [thread overview]
Message-ID: <19950818184223.EiDgThJKUkVqwFrLGMUdPpP70IVEmifh2b1ytGckxW0@z> (raw)
rwolff@noao.edu (Richard Wolff) writes:
| I'm curious as to how errata are going to be handled over the long
| run.
Or even over the short run... by now the pcdist images
have diverged a lot from the source on the cdrom.
next reply other threads:[~1995-08-18 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-18 18:42 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-17 23:06 errata Richard
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=19950818184223.EiDgThJKUkVqwFrLGMUdPpP70IVEmifh2b1ytGckxW0@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).