From: Jacob Keller <jacob.keller@gmail.com>
Date: Fri, 26 Feb 2016 08:15:46 GMT
Subject: Re: Fwd: git clone does not respect command line options
Message-ID: <CA+P7+xpuiUQgWYRgVrwKkv27KiJGQ0COrR93cFzQzn2uVA6ypQ@mail.gmail.com>
In-Reply-To: <20160226075948.GA26994@sigill.intra.peff.net>

On Thu, Feb 25, 2016 at 11:59 PM, Jeff King <peff@peff.net> wrote:
> Right. The "git-config" program doesn't know about the semantics of
> particular values (remember that in the early days, there were many
> porcelains which built on top of git, and they could all store their own
> config). Using "--get" implements "last one wins" semantics, which
> is what most config variables want. You can use "--get-all" to see all
> instances of a multi-valued variable.
>

And note that several libraries of hooks and git extensions store
configuration there as well, not just traditional porcelain. (Though
maybe that is considered porcelain? Not really sure on the term here).
I do this myself for several custom git hooks.

Thanks,
Jake