Re: What's cooking in git.git (May 2023, #04; Thu, 11)

From: Taylor Blau <me@ttaylorr.com>
Date: May 12, 2023, 03:05 UTC
Message-ID: <ZF2tDgngoBHZojLf@nand.local>
In-Reply-To: <CAMP44s0GAiFhoHFo4Ex464utf2Jm1F-LEdX2PZdUGEdp5x6Liw@mail.gmail.com>

On Thu, May 11, 2023 at 08:36:36PM -0500, Felipe Contreras wrote:

Show 13 quoted lines

> Junio C Hamano wrote:
> > * ds/merge-tree-use-config (2023-05-10) 1 commit
> >   (merged to 'next' on 2023-05-11 at e0dab53028)
> >  + merge-tree: load default git config
> >
> >  Allow git forges to disable replace-refs feature while running "git
> >  merge-tree".
> >
> >  Will merge to 'master'.
> >  source: <pull.1530.git.1683745654800.gitgitgadget@gmail.com>
>
> Why was this series merged after only 11 minutes of review window? Are patches
> from GitHub favored over all others?

Certainly not.

The reason that this was merged quickly is because both of the first two reviewers had already seen the patch and reviewed it earlier on the git-security list. The patch that Stolee sent was urgent enough to merit a quick merge. But it was not so urgent as to do an embargoed release since the client-side attack isn't interesting, rather it was important for forges which may use merge-tree directly to perform merges.

Thanks, Taylor