Re: [PATCH 4/4] config: allow including config from repository blobs

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 27, 2012, 05:30 UTC
Message-ID: <7vd3a51zlb.fsf@alter.siamese.dyndns.org>
In-Reply-To: <20120127004902.GA15257@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 8 quoted lines

> No, I meant it explicitly to be about this single user hating it. Note
> how the resulting commits are never pushed. It is purely a local
> override, but with the added bonus that history is tracked so you can
> merge in further changes from upstream.
> ...
> It also does allow "[include]ref = origin/meta:gitconfig" if you want to
> live dangerously. I consider that a feature, because it lets the user
> make the security tradeoff they deem appropriate.

While I do not think origin/meta:config is a sensible default, I actually do think that:

	[include]
        	ref = meta:gitconfig
        [branch "meta"]
		remote = origin
        	merge = refs/heads/meta

makes some sense. The earlier example with the in-tree dev_tools/config in the same line of history as the usual source material to keep track of private changes ("this single user hating it") was not realistic as it forbids the user from sharing the rest of the source once she decides to fork the config preference.