From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jeff King <peff@peff.net>
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 16:34:49 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0806181632080.2907@woody.linux-foundation.org> (raw)
In-Reply-To: <20080618231316.GB23053@sigill.intra.peff.net>
On Wed, 18 Jun 2008, Jeff King wrote:
>
> It seems like the '.' implies hierarchy, but the syntax of the file
> doesn't really follow it. But that's a minor issue, and really not worth
> the pain it would take to change at this point.
Hierarchy is idiotic in a human-readable file. It's not how people work.
And you're looking at the wrong part. You're looking at the _code_ part,
which is not the primary thing. The primary thing is the config file
syntax. And
[branch "mybranch"]
url = xyz
is a hell of a lot more readable than any alternatives I've ever seen, and
no, there is no hierarchy _anywhere_ there, and shouldn't be.
Forget about "branch.mybranch.url". It has no meaning. It's not what you
are supposed to ever use as a human (it's purely for scripting). It's not
worth even thinking about.
Linus
next prev parent reply other threads:[~2008-06-18 23:36 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 [this message]
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
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.LFD.1.10.0806181632080.2907@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=dbueno@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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;
as well as URLs for NNTP newsgroup(s).