From: Rich Salz <rsalz@bbn.com>
To: byron@archone.tamu.edu
Cc: rc@archone.tamu.edu
Subject: Re: configuration parameters
Date: Fri, 14 Feb 1992 08:15:02 -0600 [thread overview]
Message-ID: <9202141415.AA06886@litchi.bbn.com> (raw)
I think your new scheme is a little better, if only because I find the
explanations easier to read (not sure why, I just do). You might want to
think about shipping "config.h-dist" and force people to at least review
it before copying it into config.h. (People who love the defaults can
just symlink it.)
If you start using imake, I'll cry.
/r$
next reply other threads:[~1992-02-14 14:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-02-14 14:15 Rich Salz [this message]
-- strict thread matches above, loose matches on Subject: below --
1992-02-16 19:58 Alan Hargreaves
1992-02-17 15:35 ` jew
1992-02-14 23:20 rjc
1992-02-14 19:01 Tom Culliton x2278
1992-02-14 18:25 Tom Culliton x2278
1992-02-14 5:19 Byron Rakitzis
1992-02-14 5:33 ` Chris Siebenmann
1992-02-14 17:41 ` Brendan Kehoe
1992-02-14 18:24 ` Chris Siebenmann
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=9202141415.AA06886@litchi.bbn.com \
--to=rsalz@bbn.com \
--cc=byron@archone.tamu.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).