Re: What's cooking in git.git (Jun 2023, #02; Tue, 6)

From: Junio C Hamano <gitster@pobox.com>
Date: Jun 12, 2023, 17:55 UTC
Message-ID: <xmqq8rcobm5b.fsf@gitster.g>
In-Reply-To: <e08f5cea-67dc-6b96-098f-118934c11b6d@github.com>

Derrick Stolee <derrickstolee@github.com> writes:

Show 13 quoted lines

> On 6/5/2023 9:50 PM, Junio C Hamano wrote:
>
>> * ds/add-i-color-configuration-fix (2023-06-06) 1 commit
>>  - add: check color.ui for interactive add
>> 
>>  The reimplemented "git add -i" did not honor color.ui configuration.
>> 
>>  Will merge to 'next'?
>>  source: <pull.1541.git.1685994164018.gitgitgadget@gmail.com>
>
> Your recommendation to compare the raw output to the color-decoded output
> is a clean way to simplify the test (and remove the whitespace errors in
> the meantime). I'll send a v2 soon with that change.

Thanks; I saw the update plus its 2/1 suggested by Phillp.

Show 14 quoted lines

>> * ds/disable-replace-refs (2023-06-03) 3 commits
>>  - repository: create read_replace_refs setting
>>  - replace-objects: create wrapper around setting
>>  - repository: create disable_replace_refs()
>>  (this branch uses tb/pack-bitmap-traversal-with-boundary.)
>> 
>>  Introduce a mechanism to disable replace refs globally and per
>>  repository.
>> 
>>  Will merge to 'next'.
>>  source: <pull.1537.v2.git.1685716157.gitgitgadget@gmail.com>
>
> Please be sure to pick up v3 [1], which fixes a compilation bug in
> v2's patch 2. Want to keep history bisectable.

Thanks, will do.