From: Daniel Barkalow <barkalow@iabervon.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jeff King <peff@peff.net>, 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 22:10:51 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.1.00.0806182202030.19665@iabervon.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0806181726550.2907@woody.linux-foundation.org>
On Wed, 18 Jun 2008, Linus Torvalds wrote:
> On Wed, 18 Jun 2008, Linus Torvalds wrote:
> >
> > Nobody should ever use "git-config" normally. You should fire up your
> > editor and just edit the damn file in place. But no, we don't have a
> > man-page for that.
>
> Btw, one reason people end up talking about git-config is that it's easier
> to tell *other* people to "run this command" than it is to tell them to
> "edit this file so it looks like <xyz>".
The other factor is that you sometimes want to tell somebody one option
setting, and you're using a medium where there's a comprehension cost to
newlines. So 'remote.origin.url blah' is more clear than '[remote
"origin"]
url = blah' in those contexts. And we don't seem to encourage
'[remote origin] url = blah', even though it turns out to work fine (at
least, I didn't know until I just now tried it that I could suggest it).
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2008-06-19 2:12 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 [this message]
2008-06-19 0:32 ` Junio C Hamano
2008-06-19 1:23 ` Jeff King
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=alpine.LNX.1.00.0806182202030.19665@iabervon.org \
--to=barkalow@iabervon.org \
--cc=dbueno@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--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.