Re: [PATCH 0/4] Support server option from configuration

From: Patrick Steinhardt <ps@pks.im>
Date: Sep 3, 2024, 10:09 UTC
Message-ID: <ZtbgYniS6UKT9i-O@pks.im>
In-Reply-To: <pull.1776.git.git.1725279236.gitgitgadget@gmail.com>

On Mon, Sep 02, 2024 at 12:13:52PM +0000, blanet via GitGitGadget wrote:

Show 17 quoted lines

> Currently, server options for Git protocol v2 can only be specified via the
> command line option "--server-option ", which is inconvenient for users who
> want to specify a list of default options.
> 
> This patch series introduces a new multi-valued configuration,
> fetch.serverOption, to specify default server options. Designed similarly to
> push.pushOption:
> 
>  1. Server options set in lower-priority configuration files (e.g.,
>     /etc/gitconfig or $HOME/.gitconfig) can be overridden or unset in more
>     specific repository configurations using an empty string.
>  2. Command-line specified server options take precedence over those from
>     the configuration.
> 
> All commands involving server options, including git-fetch, git-clone,
> git-ls-remote, and git-pull, have been updated to recognize the new
> configuration.

It would be nice to learn about the context this comes from. In which scenario does it make sense to specify options by default? What is the intended usecase? I'm sure that this feature proposal comes from a specific usecase that you have at your employer, so learning a bit about it would help to decide whether it makes sense to have or not.

Patrick