rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: mycroft@gnu.ai.mit.edu
To: alan@jayg.astro.wisc.edu
Cc: rc@hawkwind.utcs.toronto.edu
Subject: FAQ system list
Date: Tue, 15 Jun 1993 19:25:46 -0400	[thread overview]
Message-ID: <9306152325.AA24562@hal.gnu.ai.mit.edu> (raw)
In-Reply-To: Alan Watson's message of Tue, 15 Jun 1993 19:18:10 -0400 <9306152318.AA15996@jayg.astro.wisc.edu>

Here are the environments I'm running it in which you didn't list:

	       Sun 68k	      SunOS v4.1.1_U1     gcc
	       i386/i486      NetBSD		  cc (which is gcc v1.39)
	       i386/i486      NetBSD		  gcc (v2)
	       RS/6000	      AIX 3.2.1		  cc

  reply	other threads:[~1993-06-15 23:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-06-15 23:18 Alan Watson
1993-06-15 23:25 ` mycroft [this message]
1993-06-29  4:15 ` rc on Linux? Dave Mason
1993-06-16  2:27 FAQ system list Tom Culliton x2278
1993-06-16  7:34 noel
1993-06-16 15:02 Alan Watson
1993-06-16 16:52 ` mycroft
     [not found] <alan@oldp.astro.wisc.edu>
1993-06-16 17:38 ` malte
1993-06-16 17:41   ` Chris Siebenmann
1993-06-18 10:57 Stefan Dalibor

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9306152325.AA24562@hal.gnu.ai.mit.edu \
    --to=mycroft@gnu.ai.mit.edu \
    --cc=alan@jayg.astro.wisc.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \


* 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).