ab/ambiguous-object-name & ab/only-single-progress-at-once (was: What's cooking in git.git (Feb 2022, #04; Tue, 15))
- From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
- Date
- Feb 15, 2022, 22:22 UTC
- Message-ID
- <220215.861r03wywm.gmgdl@evledraar.gmail.com>
- In-Reply-To
- <xmqqk0dwyrcv.fsf@gitster.g>
On Tue, Feb 15 2022, Junio C Hamano wrote:
Show 30 quoted lines
> * ab/ambiguous-object-name (2022-01-27) 7 commits
> - object-name: re-use "struct strbuf" in show_ambiguous_object()
> - object-name: iterate ambiguous objects before showing header
> - object-name: show date for ambiguous tag objects
> - object-name: make ambiguous object output translatable
> - object-name: explicitly handle bad tags in show_ambiguous_object()
> - object-name: explicitly handle OBJ_BAD in show_ambiguous_object()
> - object-name tests: add tests for ambiguous object blind spots
>
> Error output given in response to an ambiguous object name has been
> improved.
>
> Will merge to 'next'?
> source: <cover-v8-0.7-00000000000-20220127T052116Z-avarab@gmail.com>
> [...]
> * ab/only-single-progress-at-once (2022-02-03) 9 commits
> - pack-bitmap-write.c: don't return without stop_progress()
> - progress API: unify stop_progress{,_msg}(), fix trace2 bug
> - progress.c: refactor stop_progress{,_msg}() to use helpers
> - progress.c: use dereferenced "progress" variable, not "(*p_progress)"
> - progress.h: format and be consistent with progress.c naming
> - progress.c tests: test some invalid usage
> - progress.c tests: make start/stop commands on stdin
> - progress.c test helper: add missing braces
> - leak tests: fix a memory leak in "test-progress" helper
>
> Further tweaks on progress API.
>
> Will merge to 'next'?
> source: <cover-v9-0.9-00000000000-20220203T213350Z-avarab@gmail.com>Both of these are, I think, good to merge to "next" in their current state.