From: Taylor Blau <me@ttaylorr.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>
Subject: Re: What's cooking in git.git (May 2023, #04; Thu, 11)
Date: Thu, 11 May 2023 23:05:50 -0400 [thread overview]
Message-ID: <ZF2tDgngoBHZojLf@nand.local> (raw)
In-Reply-To: <CAMP44s0GAiFhoHFo4Ex464utf2Jm1F-LEdX2PZdUGEdp5x6Liw@mail.gmail.com>
On Thu, May 11, 2023 at 08:36:36PM -0500, Felipe Contreras wrote:
> 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
next prev parent reply other threads:[~2023-05-12 3:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 0:39 What's cooking in git.git (May 2023, #04; Thu, 11) Junio C Hamano
2023-05-12 1:36 ` Felipe Contreras
2023-05-12 3:05 ` Taylor Blau [this message]
2023-05-12 3:46 ` Felipe Contreras
2023-05-12 7:13 ` ps/fetch-output-format (was: What's cooking in git.git (May 2023, #04; Thu, 11)) Patrick Steinhardt
2023-05-12 19:33 ` ps/fetch-output-format Junio C Hamano
2023-05-12 15:26 ` tl/push-branches-is-an-alias-for-all (Was: Re: What's cooking in git.git (May 2023, #04; Thu, 11)) Elijah Newren
2023-05-12 17:23 ` tl/push-branches-is-an-alias-for-all Junio C Hamano
2023-05-12 20:52 ` What's cooking in git.git (May 2023, #04; Thu, 11) brian m. carlson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZF2tDgngoBHZojLf@nand.local \
--to=me@ttaylorr.com \
--cc=derrickstolee@github.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).