Patrick Steinhardt <ps@xxxxxx> writes: > On Tue, Oct 08, 2024 at 03:38:14AM +0000, blanet via GitGitGadget wrote: >> We manage some internal repositories with numerous CI tasks, each requiring >> code preparation through git-clone or git-fetch. These tasks, triggered by >> post-receive hooks, often fetch the same copy of code concurrently using >> --depth=1, causing extremely high load spikes on our Git servers. >> ... >> This patch series introduces a new multi-valued configuration, >> remote.<name>.serverOption, similar to push.pushOption, to specify default >> server options for the corresponding remote. >> >> * Patches 1~3 contain the main changes for introducing the new >> configuration. >> * Patch 4 fixes a issue for git-fetch not sending server-options when >> fetching from multiple remotes. >> * Patch 5 is a minor fix for a server options-related memory leak. >> >> 1. https://git-scm.com/docs/git-config#Documentation/git-config.txt-uploadpackpackObjectsHook >> 2. https://git-scm.com/docs/gitprotocol-v2#_server_option > > The range-diff looks as expected to me, so this should be ready > to go from my point of view. Thanks! Thanks, both of you. Queued.
