From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Thoma Paulsen <thomas.paulsen@firemail.de>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] A question about ls(1)
Date: Sun, 28 Apr 2019 20:53:05 -0400 [thread overview]
Message-ID: <CAC0cEp9Ug-R4TAKcQPNcjowAu5Oc+jDnvfHC8XFWMoizdWZLcg@mail.gmail.com> (raw)
In-Reply-To: <9ba54618abe5976097f2733ed3eef254@firemail.de>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
I have a deep-seated distrust of global stuff. In C, obviously. But also
for things like git configs, which may differ substantially for different
directories (one for each project). I cannot imagine trying to control such
things in a single place. Seems intensely ugly.
On Sun, Apr 28, 2019 at 6:47 PM Thoma Paulsen <thomas.paulsen@firemail.de>
wrote:
> Von: Jon Forrest <nobozo@gmail.com>
>
> > One of the things I think Windows did right was to have one
> > place where all configuration information is kept. Sure,
> > you can argue about the implementation details, but Windows
> > doesn't have configuration files all over the place.
> >
> in theories - yes, in real there are a lot of configuration files all over
> the place.
>
>
>
[-- Attachment #2: Type: text/html, Size: 1253 bytes --]
next prev parent reply other threads:[~2019-04-29 0:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 16:54 Norman Wilson
2019-04-28 19:45 ` Jon Forrest
2019-04-28 20:00 ` Bakul Shah
2019-04-29 18:05 ` Michael Kjörling
2019-04-29 20:37 ` Warner Losh
2019-04-29 20:44 ` Christopher Browne
2019-04-30 6:44 ` Michael Kjörling
2019-04-30 7:24 ` Kurt H Maier
2019-04-30 10:35 ` Wesley Parish
2019-04-29 22:32 ` Bakul Shah
2019-04-30 11:52 ` Theodore Ts'o
2019-04-28 22:16 ` Thoma Paulsen
2019-04-29 0:53 ` John P. Linderman [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-04-27 23:03 Noel Chiappa
2019-04-27 20:11 Norman Wilson
2019-04-27 14:16 Anthony Martin
2019-04-27 15:38 ` Warner Losh
2019-04-27 15:42 ` Larry McVoy
2019-04-28 23:59 ` Warner Losh
2019-04-28 11:47 ` Dan Cross
2019-04-28 12:00 ` arnold
2019-04-28 14:44 ` jcs
2019-04-28 16:15 ` Bakul Shah
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=CAC0cEp9Ug-R4TAKcQPNcjowAu5Oc+jDnvfHC8XFWMoizdWZLcg@mail.gmail.com \
--to=jpl.jpl@gmail.com \
--cc=thomas.paulsen@firemail.de \
--cc=tuhs@minnie.tuhs.org \
/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).