From: Jeff King <peff@peff.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Denis Bueno <dbueno@gmail.com>
Subject: Re: [PATCH 1/4] Split up default "core" config parsing into helper routine
Date: Wed, 18 Jun 2008 21:23:10 -0400 [thread overview]
Message-ID: <20080619012310.GA25307@sigill.intra.peff.net> (raw)
In-Reply-To: <alpine.LFD.1.10.0806181721580.2907@woody.linux-foundation.org>
On Wed, Jun 18, 2008 at 05:23:21PM -0700, Linus Torvalds wrote:
> > Have you read "man git-config" lately?
>
> That whole program is there just for scripting. Of _course_ it talks about
> the machine format!
Forget the command git-config; all of the config _variables_ are
documented in "foo.bar" form. Name one place in all of the documentation
where the user can find out about core.pager, but the "foo.bar" form is
not used.
-Peff
next prev parent reply other threads:[~2008-06-19 1:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 22:29 [PATCH 0/4] Add 'core.fsyncobjectfiles' config option Linus Torvalds
2008-06-18 22:30 ` [PATCH 1/4] Split up default "core" config parsing into helper routine Linus Torvalds
2008-06-18 22:31 ` [PATCH 2/4] Split up default "user" " Linus Torvalds
2008-06-18 22:31 ` [PATCH 3/4] Split up default "i18n" and "branch" config parsing into helper routines Linus Torvalds
2008-06-18 22:32 ` [PATCH 4/4] Add config option to enable 'fsync()' of object files Linus Torvalds
2008-06-18 22:49 ` [PATCH 1/4] Split up default "core" config parsing into helper routine Jeff King
2008-06-18 22:58 ` Linus Torvalds
2008-06-18 23:13 ` Jeff King
2008-06-18 23:34 ` Linus Torvalds
2008-06-19 0:08 ` Jeff King
2008-06-19 0:23 ` Linus Torvalds
2008-06-19 0:28 ` Linus Torvalds
2008-06-19 2:10 ` Daniel Barkalow
2008-06-19 0:32 ` Junio C Hamano
2008-06-19 1:23 ` Jeff King [this message]
2008-06-19 0:18 ` Eric Raible
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=20080619012310.GA25307@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dbueno@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.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.