Re: [PATCH v2] config: introduce an Operating System-specific `includeIf` condition

From: Jeff King <peff@peff.net>
To: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Phillip Wood" <phillip.wood123@gmail.com>,
	"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v2] config: introduce an Operating System-specific `includeIf` condition
Date: Mon, 21 Nov 2022 18:32:11 -0500	[thread overview]
Message-ID: <Y3wKe7aO7I7bpmLm@coredump.intra.peff.net> (raw)
In-Reply-To: <pull.1429.v2.git.1669058388327.gitgitgadget@gmail.com>

On Mon, Nov 21, 2022 at 07:19:48PM +0000, Johannes Schindelin via GitGitGadget wrote:

> It is relatively common for users to maintain identical `~/.gitconfig`
> files across all of their setups, using the `includeIf` construct
> liberally to adjust the settings to the respective setup as needed.

This seems like a reasonable thing to have in general, but I wonder if
you have an example of how people use this. Mostly I am wondering:

  - is it sometimes a misuse, where users _think_ that the OS is
    correlated with some feature of Git.  And they would be better off
    with some flag like "does the current platform support fsmonitor".

  - for cases where it really  is "uname -s" the best differentiator? Or
    would they commonly want to lump FreeBSD and Linux into the same
    category, or to tell the difference between Debian versus Fedora?

-Peff