Re: What's cooking in git.git (May 2022, #05; Mon, 16)

From: Derrick Stolee <derrickstolee@github.com>
Date: May 17, 2022, 13:10 UTC
Message-ID: <789a0510-63b3-b297-ff35-de752d4f64d6@github.com>
In-Reply-To: <xmqq5ym4zpmn.fsf@gitster.g>

On 5/17/2022 1:37 AM, Junio C Hamano wrote:

Show 10 quoted lines

> * tb/midx-race-in-pack-objects (2022-05-13) 2 commits
>  - builtin/pack-objects.c: ensure pack validity from MIDX bitmap objects
>  - pack-bitmap: check preferred pack validity when opening MIDX bitmap
> 
>  The multi-pack-index code did not protect the packfile it is going
>  to depend on from getting removed while in use, which has been
>  corrected.
> 
>  Will merge to 'next'?
>  source: <cover.1652458395.git.me@ttaylorr.com>

Looking at the conversation here, I would change this to "expecting a re-roll".

Show 13 quoted lines

> * ab/valgrind-fixes (2022-05-12) 4 commits
>   (merged to 'next' on 2022-05-16 at 75d760528f)
>  + commit-graph.c: don't assume that stat() succeeds
>  + object-file: fix a unpack_loose_header() regression in 3b6a8db3b03
>  + log test: skip a failing mkstemp() test under valgrind
>  + tests: using custom GIT_EXEC_PATH breaks --valgrind tests
>  (this branch is used by ds/object-file-unpack-loose-header-fix.)
> 
>  A bit of test framework fixes with a few fixes to issues found by
>  valgrind.
> 
>  Will merge to 'master'.
>  source: <20220512223218.237544-1-gitster@pobox.com>

...

Show 8 quoted lines

> * ds/object-file-unpack-loose-header-fix (2022-05-16) 1 commit
>  - object-file: convert 'switch' back to 'if'
>  (this branch uses ab/valgrind-fixes.)
> 
>  Coding style fix.
> 
>  Will merge to 'next'?
>  source: <377be0e9-8a0f-4a86-0a66-3b08c0284dae@github.com>

With ab/valgrind-fixes in 'next', I think this is an easy one to merge. I'm calling it out here since the patch was hidden in the review of ab/valgrind-fixes.

Thanks, -Stolee