From: Vincent Broman <broman@nosc.mil>
To: imurdock@debian.org
Cc: rc@hawkwind.utcs.toronto.edu
Subject: Update for Debian shells/rc-1.4-2
Date: Thu, 27 Feb 1997 14:02:53 -0500 [thread overview]
Message-ID: <19970227190253.9146.qmail@np.nosc.mil> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Ian Murdock,
I took the liberty of updating the Debian package for
the Plan 9 shell, rc-1.4-2, and putting my results at
ftp://archimedes.nosc.mil/pub/transfer/rc-1.4-3.*
for your approval and use. The MD5 hashes should be:
6a23918e5475e0e1b3eb5a8c3a1fc3e8 rc-1.4-3.deb
7a45fcf4a699f7fe9c234ce3c2947c00 rc-1.4-3.diff.gz
4bf23163eff4dc730d50fc5647a7d968 rc-1.4-3.tar.gz
The diffs/patches might have a problem with a file "trip.rc"
which contains a nul character.
There isn't anyone actively maintaining rc just now,
and there are many volunteer patches for rc floating
around on its mailing list. I've installed the clearest
bug fixes and most popular enhancements that would command
general approval, I think. One critical bug fix takes
care of the problem that 1.4-2 would die whenever you hit
Control-C! I've tested this code on Linux 2.0 and on SunOS 4.1.3.
Vincent Broman, code D783 Bayside Email: broman@nosc.mil
Naval Command Control and Ocean Surveillance Center, RDT&E Div.
San Diego, CA 92152-6222, USA Phone: +1 619 553 1641
=== PGP protected mail preferred. For public key finger broman@np.nosc.mil ===
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMxXZxmCU4mTNq7IdAQHtUwQAsMRQXOLtSZ8RjrAC0P7tWFj0Jac+jsEv
k01ro3fzM2SGxcA5pzvgYTZVy3yDoKFR5IARCzzC10y6hUk0ekAt26xwVG0Nic0u
/L/aNP7ZaUsYW3rbJy7NXn/Paq1SAGeLrQ4Zg504vtBqM+SsxfjiKWwwd2bMfH94
bf9jv7Ic8OU=
=5Aj9
-----END PGP SIGNATURE-----
next reply other threads:[~1997-02-27 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-27 19:02 Vincent Broman [this message]
1997-02-27 19:55 ` Scott Schwartz
1997-03-03 19:09 Byron Rakitzis
1997-03-04 3:34 ` David Luyer
1997-03-04 3:51 ` Soren Dayton
1997-03-04 17:33 ` Peter Koch
1997-03-04 19:08 ` Scott Schwartz
1997-03-04 2:01 Tom Culliton
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=19970227190253.9146.qmail@np.nosc.mil \
--to=broman@nosc.mil \
--cc=imurdock@debian.org \
--cc=rc@hawkwind.utcs.toronto.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).