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 BD0981F463 for ; Sat, 21 Dec 2019 02:37:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726733AbfLUChc (ORCPT ); Fri, 20 Dec 2019 21:37:32 -0500 Received: from pb-smtp1.pobox.com ([64.147.108.70]:54020 "EHLO pb-smtp1.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726571AbfLUChc (ORCPT ); Fri, 20 Dec 2019 21:37:32 -0500 Received: from pb-smtp1.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id F005A3BFC2; Fri, 20 Dec 2019 21:37:29 -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=UVqmMjOAvUbRAzXHo4rMowijlt8=; b=n+tysP xf+aMIozIB/nMCfH+iBBVtYCGmXwkId5UyFXHDJ13iPOZ6Z6s9sEvjspaJi6q1pv 0UrT08Xc/0HCfaZ59x6DCsRitvEQoQI8gk/NjF+c45r0L+SzcfspfGRXwyHOxHw7 oBNCijtIg3UXg+b+59ErqQ9+DfxobGtUKwMC8= 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=cRP9B/L/pN9LJC/AlofKhvxzBd95Im43 N2YcpPJSzL8fABrQy7kxFEgkZBIn5GB3fwIaB43UAq48HWxuKAqLZoHWCiSgPiVR EJRy9D1YB4H7tgFsHD0Q+9dHIZI8RPgXau3dSg6H4DiAjSV+JbBeSCRlY/wMksO6 KNMhgcrhKV4= Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id E7C5D3BFC1; Fri, 20 Dec 2019 21:37:29 -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-smtp1.pobox.com (Postfix) with ESMTPSA id 502A03BFC0; Fri, 20 Dec 2019 21:37:29 -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: Fri, 20 Dec 2019 18:37:27 -0800 In-Reply-To: (Matt Rogers's message of "Fri, 20 Dec 2019 17:58:22 -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: D4FC3842-239A-11EA-8201-C28CBED8090B-77302942!pb-smtp1.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Matt Rogers writes: > Philip, > >>The commit message doesn't fully highlight that the config list will >>often be all the users config values, so each value will be >>disambiguated/identified as to it's origin. > > I don't really understand what you mean by "it's origin" here. When > you say origin, do you mean in the "--show-origin" sense of "file/blob/etc." > or something else? Because scope is kind of an orthogonal concept to origin > in that sense as you can have files with different origins but the same scope. I do not think origin and scope are orghogonal, though. Can the same file appear as the source for different configuration var-value pair in two different scopes? It is likely that you can _guess_ with high precision that given a pathname reported by --show-origin what scope it is in. It on the other hand is not so trivial given a scope to guess which exact file a var-value pair came from, I would think.\