Re: [PATCH] merge-tree: load default git config

From: Derrick Stolee <derrickstolee@github.com>
Date: May 10, 2023, 19:26 UTC
Message-ID: <cc058647-554b-3b40-b8b9-52de0b7bd9e4@github.com>
In-Reply-To: <xmqqsfc43si0.fsf@gitster.g>

On 5/10/2023 3:18 PM, Junio C Hamano wrote:

Show 12 quoted lines

> "Derrick Stolee via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 
>>     This patch was reviewed on the Git security list, but the impact seemed
>>     limited to Git forges using merge-ort to create merge commits. The
>>     forges represented on the list have deployed versions of this patch and
>>     thus are no longer vulnerable.
> 
> Let's queue directly on 'next' (unlike 'master', where we want to
> merge only commits that had exposure in 'next' for a week or so,
> there is no formal requirement for topics to enter 'next' before
> spending any time in 'seen') and fast-track to 'master', as I've
> seen it already reviewed adequately over there.

Thanks for picking it up so quickly. I did not mean to imply that we should merge to master without giving the public list time to digest the patch. It is a rather simple one, though.

Thanks, -Stolee