rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Bengt Kleberg <bengtk@damek.kth.se>
To: byron@netapp.com, rc@hawkwind.utcs.toronto.edu
Subject: Re: autoconfig
Date: Wed, 2 Apr 1997 04:38:59 -0500	[thread overview]
Message-ID: <199704020938.LAA17494@ankaret.damek.kth.se> (raw)

> My conclusion: It seems that rc + an autoconfig script could take
> out all the configuration options. I don't see the point of going
> with Posix, then.
 Posix feels more "professional" than autoconfig. Perhaps I'm just very vain.


             reply	other threads:[~1997-04-02  9:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-02  9:38 Bengt Kleberg [this message]
1997-04-03  0:15 ` autoconfig Scott Merrilees
1997-04-03  3:14   ` autoconfig Warren Toomey
  -- strict thread matches above, loose matches on Subject: below --
1997-04-05 18:38 autoconfig Bengt Kleberg
1997-04-02 20:24 autoconfig Byron Rakitzis
1997-04-02 17:30 autoconfig Rich Salz
1997-04-01 23:52 autoconfig Alan Watson
1997-04-01 19:28 autoconfig Byron Rakitzis
1997-04-02  1:11 ` autoconfig Greg A. Woods
1997-04-02  8:32   ` autoconfig Stefan Dalibor
1997-04-02  2:20 ` autoconfig Scott Schwartz
1997-04-02 15:10   ` autoconfig Mark K. Gardner
1997-04-02  2:59 ` autoconfig David Luyer
1997-04-02 16:32 ` autoconfig Chet Ramey

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=199704020938.LAA17494@ankaret.damek.kth.se \
    --to=bengtk@damek.kth.se \
    --cc=byron@netapp.com \
    --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).