From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Tue, 9 Dec 2003 13:33:53 -0500 [thread overview]
Message-ID: <20031209183353.GA5257@sigint.cs.purdue.edu> (raw)
In-Reply-To: <200312090454.hB94skl24638@augusta.math.psu.edu>
On Mon, Dec 08, 2003 at 11:54:45PM -0500, Dan Cross wrote:
> But, what's a better alternative? I'm all eyes.
The Windows registry? *ducks*
I have to agree with Charles and Geoff. The only thing .local files buy
you is overwrite protection, which is already provided by pull. You still
have to check that your overrides in .local are valid. Is there a way
around that problem that doesn't involve Star Trek-type AI or mind reading?
Ultimately, it's the price one pays for the flexibility of expressing
configuration info as shell scripts instead of a database (or registry)
of predetermined, paramaterized, versioned configuration variables.
next prev parent reply other threads:[~2003-12-09 18:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 12:48 David Presotto
2003-12-08 15:10 ` andrey mirtchovski
2003-12-08 16:21 ` David Presotto
2003-12-08 19:30 ` Dan Cross
2003-12-08 21:14 ` david presotto
2003-12-08 22:20 ` Dan Cross
2003-12-09 0:55 ` David Presotto
2003-12-09 1:20 ` Russ Cox
2003-12-09 1:29 ` Dan Cross
2003-12-09 1:36 ` Russ Cox
2003-12-09 3:00 ` Dan Cross
2003-12-09 4:02 ` Geoff Collyer
2003-12-09 3:44 ` mirtchov
2003-12-09 4:10 ` Scott Schwartz
2003-12-07 9:59 ` Charles Forsyth
2003-12-07 10:28 ` Charles Forsyth
2003-12-09 4:33 ` Geoff Collyer
2003-12-09 4:54 ` Dan Cross
2003-12-09 7:47 ` okamoto
2003-12-09 11:23 ` a
2003-12-09 12:12 ` boyd, rounin
2003-12-09 18:33 ` splite [this message]
2003-12-09 19:23 ` Brantley Coile
-- strict thread matches above, loose matches on Subject: below --
2003-12-09 7:55 YAMANASHI Takeshi
2003-12-09 13:49 ` David Presotto
2003-12-08 11:36 Tiit Lankots
2003-12-08 14:51 ` ron minnich
2003-12-08 15:00 ` Russ Cox
2003-12-08 10:08 Sujan Gautam
2003-12-08 13:53 ` mirtchov
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=20031209183353.GA5257@sigint.cs.purdue.edu \
--to=splite@purdue.edu \
--cc=9fans@cse.psu.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).