From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-4.0 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 48B801F463 for ; Sat, 21 Dec 2019 23:47:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726768AbfLUXr6 (ORCPT ); Sat, 21 Dec 2019 18:47:58 -0500 Received: from pb-smtp21.pobox.com ([173.228.157.53]:61782 "EHLO pb-smtp21.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726066AbfLUXr6 (ORCPT ); Sat, 21 Dec 2019 18:47:58 -0500 Received: from pb-smtp21.pobox.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 961D9AAE1F; Sat, 21 Dec 2019 18:47:57 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=Vf9020MnGup+vh7F1Dyu9EohSbo=; b=u8pPR/ 4BHTRKH6/a6bDkZRS4dpsyRjFJgEgFvdSUkaDOLKKm4kTmBLfMw6CYkVdTRxDP5L 5s2ZBGZd5WylxZDXHSilaNedP8xu1IfhwDoKppFr1WICBJNB+jDh1IstE9mjPMal mrFqcZCBLUjQVu3CCQUkkmT5QnLymaDnNpdQ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; q=dns; s=sasl; b=QgqkybT9CeOukFKdIse0/wPRUP7UN1Q4 ZJLrlZUEMEztM2y3DlsSGtQAk3Y5xS31EmhY1vcYNegjl47z0XOhhsQVcScpSJ9T WX55zCYNB/tjnx8uPJrrbz8q3nEFBRRB/zPAhDIS8kYnE8xM1A9csFm136P+NBPv MneLQYuuehY= Received: from pb-smtp21.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp21.pobox.com (Postfix) with ESMTP id 8E572AAE1E; Sat, 21 Dec 2019 18:47:57 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [34.76.80.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp21.pobox.com (Postfix) with ESMTPSA id B99C8AAE1D; Sat, 21 Dec 2019 18:47:54 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Matt Rogers Cc: Philip Oakley , Matthew Rogers via GitGitGadget , git@vger.kernel.org Subject: Re: [PATCH 1/1] config: allow user to know scope of config options References: <9a91caa0-72c3-3a38-3eb7-55a43537762e@iee.email> <03b001d5b601$09b950e0$1d2bf2a0$@gmail.com> Date: Sat, 21 Dec 2019 15:47:52 -0800 In-Reply-To: (Matt Rogers's message of "Fri, 20 Dec 2019 22:08:35 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 4EE1D1D8-244C-11EA-B181-8D86F504CC47-77302942!pb-smtp21.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Matt Rogers writes: > And that origin and scope correlate, but aren't necessarily > one-for-one. Yes, exactly. When I see "orthogonal", I expect the word describes things that do not correlate. I can see values in the option that gives scope but not path in order to write scripts that limits var-value pairs to be used (e.g. "I do not want to be affected by the per-repository values", "I do not trust settings that comes system-wide"). I also can see values in the option that gives only path when debugging the configuration file. I briefly wondered, for the purpose of such "I do want to see only those settings coming from these scopes" script, it may make more sense to have the command _filter_ the var-value pairs, instead of showing all of them with label, but that feature always exists ;-)