rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks@hawkwind.utcs.toronto.edu>
To: rc@archone.tamu.edu
Subject: Re: configuration parameters
Date: Thu, 13 Feb 1992 23:33:14 -0600	[thread overview]
Message-ID: <92Feb14.003318est.2716@hawkwind.utcs.toronto.edu> (raw)
In-Reply-To: byron's message of Fri, 14 Feb 92 00:19:54 -0500. <92Feb13.232005cst.45338@archone.tamu.edu>

 Actually, I'll disagree here; I think the combination of the Makefile and the
'canned' stuff in config.h has worked fine. It also (importantly!)
keeps the number of files one usually has to edit when moving
rc from platform to platform down to one (Makefile), which people
are used to editing.

	- cks


  reply	other threads:[~1992-02-14  5:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-02-14  5:19 Byron Rakitzis
1992-02-14  5:33 ` Chris Siebenmann [this message]
1992-02-14 17:41   ` Brendan Kehoe
1992-02-14 18:24     ` Chris Siebenmann
1992-02-14 14:15 Rich Salz
1992-02-14 18:25 Tom Culliton x2278
1992-02-14 19:01 Tom Culliton x2278
1992-02-14 23:20 rjc
1992-02-16 19:58 Alan Hargreaves
1992-02-17 15:35 ` jew

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=92Feb14.003318est.2716@hawkwind.utcs.toronto.edu \
    --to=cks@hawkwind.utcs.toronto.edu \
    --cc=rc@archone.tamu.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).