From: culliton@srg.af.mil (Tom Culliton x2278)
To: rc@hawkwind.utcs.toronto.edu
Subject: rc on linux
Date: Fri, 6 May 1994 13:37:32 -0400 [thread overview]
Message-ID: <9405061337.aa27148@ceres.srg.af.mil> (raw)
I built rc on my new Linux machine :-) the other night, and basically it
was just as easy as you'd expect. Running trip didn't show any obvious
problems, but there is definitely something funny going on with signals
and signal handlers. Clues?
In other news, Byron seems to have fallen off the face of the planet
again. ;-) Any further news or fixes for the problems with 1.5beta1
that we discussed a while back? Will there ever be a "real" 1.5? ;-)
Tom
reply other threads:[~1994-05-06 21:46 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 \
--in-reply-to=9405061337.aa27148@ceres.srg.af.mil \
--to=culliton@srg.af.mil \
--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).