From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Add ".git/config" file parser
Date: Mon, 10 Oct 2005 14:50:01 -0700 [thread overview]
Message-ID: <434AE209.60605@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0510101446180.14597@g5.osdl.org>
Linus Torvalds wrote:
>
> On Mon, 10 Oct 2005, Linus Torvalds wrote:
>
>> ; core variables
>> [core]
>> ; Don't trust file modes
>> filemode = false
>>
>> ; Our diff algorithm
>> [diff]
>> external = "/usr/local/bin/gnu-diff -u"
>> renames = true
>>
>>which parses into two variables: "core.filemode" is associated with the
>>string "false", and "diff.external" gets the appropriate quoted value.
>
> _Three_ variables. Duh. I added the "renames" thing later, as I was
> looking at what kinds of default flags the "git-diff-xyz" family might be
> interested in having.
>
A suggestion: if you make your basic types (integer, string, boolean)
recognizable by the parser, you can present them in that way. This
pretty much means strings will have to always be double-quoted, but that
avoids a bunch of ambiguities.
-hpa
next prev parent reply other threads:[~2005-10-10 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 18:00 Seeing various mode changes on cygwin Jonas Fonseca
2005-10-08 18:51 ` Junio C Hamano
2005-10-08 21:36 ` Alex Riesen
2005-10-08 23:36 ` Junio C Hamano
2005-10-09 2:19 ` Linus Torvalds
2005-10-09 6:46 ` Junio C Hamano
2005-10-10 6:48 ` Daniel Barkalow
2005-10-10 7:38 ` Junio C Hamano
2005-10-10 17:59 ` Daniel Barkalow
2005-10-10 18:22 ` Linus Torvalds
2005-10-10 21:35 ` Add ".git/config" file parser Linus Torvalds
2005-10-10 21:47 ` Linus Torvalds
2005-10-10 21:50 ` H. Peter Anvin [this message]
2005-10-10 22:12 ` Linus Torvalds
2005-10-12 0:25 ` Junio C Hamano
2005-10-12 7:43 ` [PATCH] Use core.filemode Junio C Hamano
2005-10-09 3:43 ` Seeing various mode changes on cygwin H. Peter Anvin
2005-10-09 13:02 ` Alex Riesen
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=434AE209.60605@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.