From: Tim Goodwin <email@example.com> To: firstname.lastname@example.org Subject: Release rc-1.7 is now available Date: Thu, 20 Jun 2002 11:27:14 -0500 [thread overview] Message-ID: <email@example.com> (raw) I'm delighted to announce the release of rc-1.7. Apart from bumping the version number, and a couple of trivial changes to the installation documentation, this release is identical to rc-1.6c7. The release is available from the usual place: http://www.star.le.ac.uk/~tjg/rc/release/rc-1.7.tar.gz and it should also be on the UToronto FTP server soon. I've appended the NEWS file from the distribution, as a reminder of what's changed since rc-1.6. (In summary: not a lot!) A big thank you to everybody who contributed to this release. Tim. Highlights of changes since rc-1.6. See ChangeLog for further details. Portability. Many minor tweaks, including fixes for BeOS, CygWin, QNX, and gcc-3. Bug fixes. A number of bugs have been fixed. The serious ones were: a core dump, triggered by `~ () '*''; premature exit, triggered by sourcing a file which could be open()ed but not read() (such as a directory on many systems); uninterruptible looping, triggered by semantic errors in `fn prompt'; deficiencies in the `limit' builtin. New features. The following features are new: the `$version' variable replaces the `-V' flag; the `-I' flag (definitively not interactive) was added for compatibility with the Plan 9 rc; ASCII SOH (^A) is now handled transparently; support for large files; support for more process resource limits. Documentation. Distributions of this rc used to include a PostScript paper given by Tom Duff to the UKUUG, describing the Plan 9 rc. This paper is no longer distributed with rc, but instead is available on the web, both in its original PostScript version, and an updated HTML version. Tim Goodwin 2002-05-21
reply other threads:[~2002-06-20 19:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Release rc-1.7 is now available' \ /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
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).