From: Linus Torvalds <torvalds@osdl.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, junkio@cox.net
Subject: Re: [PATCH] Add config variable core.symrefsonly
Date: Tue, 15 Nov 2005 10:39:50 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0511151028540.3945@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0511151923120.1103@wbgn013.biozentrum.uni-wuerzburg.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1321 bytes --]
On Tue, 15 Nov 2005, Johannes Schindelin wrote:
>
> Linus, is there any reason you don´t allow spaces, underscores
> and dashes in the config variables?
I much preferred being anal and maybe relaxing the rules later than being
permissive and accepting horrible crap.
Spaces are definitely out, since we are trying to igore whitespace
everywhere, but underscores and dashes might be ok.
However, the traditional way to do these kinds of things in ini files is
with PrettyCaps(tm), ie you'd do
[core]
SymRefsOnly = true
rather than the C way.
Let's face it, the C way is the only true way for a programming language,
but having case matter in something unimportant and human-readable like a
"ini" file is just bothersome, so PrettyCase(tm) actually makes sense
there.
PrettyCase is for toys - unimportant things where it's more important to
say "we don't care" over saying "we need to be precise". So Pascal is PC.
It's a toy language. FAT is PC - it's a toy filesystem. And ini files are
PC: it's more important that a config file is human-readable than it is
that it's very precise and strict.
Put another way: real programmers want strict rules, because they know
they'll be hurt without them. But _users_ need to be coddled. And ini
files aren't for programmers, they are for users.
Linus
next prev parent reply other threads:[~2005-11-15 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 18:24 [PATCH] Add config variable core.symrefsonly Johannes Schindelin
2005-11-15 18:39 ` Linus Torvalds [this message]
2005-11-15 18:54 ` Johannes Schindelin
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=Pine.LNX.4.64.0511151028540.3945@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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