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

From: Derrick Stolee <derrickstolee@github.com>
Date: Jun 6, 2023, 13:35 UTC
Message-ID: <e08f5cea-67dc-6b96-098f-118934c11b6d@github.com>
In-Reply-To: <xmqq5y814aw8.fsf@gitster.g>

On 6/5/2023 9:50 PM, Junio C Hamano wrote:

Show 7 quoted lines

> * 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.

Show 11 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.

[1] https://lore.kernel.org/git/pull.1537.v3.git.1686057877.gitgitgadget@gmail.com

Thanks, -Stolee