From: "Mark K. Gardner" <mkgardne@cs.uiuc.edu>
To: rc@hawkwind.utcs.toronto.edu
Cc: byron@netapp.com
Subject: Re: Helping with RC
Date: Tue, 4 Mar 1997 09:46:58 -0500 [thread overview]
Message-ID: <199703041446.IAA09487@pertsserver.cs.uiuc.edu> (raw)
-- Byron, the Great said:
> Given that I am stuck on my own with nothing but BSD on my pc, I will
> have to ask for some volunteers to run trip tests. I'll mention it
> again on the list once I get my act together so I can incorporate
> these patches.
I volunteer to test the Solaris version of RC. I have had some trouble
in the past getting it to work correctly and want to make sure there
is an official version which supports Solaris. (Our computer support
department has standardized on Solaris and I want RC!)
Thanks for the good work in getting/keeping RC rolling. Good luck on
your music studies.
--
Mark K. Gardner (mkgardne@cs.uiuc.edu)
University of Illinois at Urbana-Champaign
Real-Time Systems Laboratory
--
next reply other threads:[~1997-03-04 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-04 14:46 Mark K. Gardner [this message]
1997-03-04 18:56 ` Scott Schwartz
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=199703041446.IAA09487@pertsserver.cs.uiuc.edu \
--to=mkgardne@cs.uiuc.edu \
--cc=byron@netapp.com \
--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).