git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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.

Previous: Ævar Arnfjörð BjarmasonNext: Elijah Newren
Message 3 of 9 in “What's cooking in git.git (Feb 2022, #04; Tue, 15)”
  1. Junio C HamanoFeb 15, 2022
  2. ja/i18n-common-messages (was: What's cooking in git.git (Feb 2022, #04; Tue, 15))Ævar Arnfjörð Bjarmason, Feb 15, 2022
  3. ab/ambiguous-object-name & ab/only-single-progress-at-once (was: What's cooking in git.git (Feb 2022, #04; Tue, 15))Ævar Arnfjörð Bjarmason, Feb 15, 2022
  4. en/present-despite-skipped (Was: Re: What's cooking in git.git (Feb 2022, #04; Tue, 15))Elijah Newren, Feb 16, 2022
  5. Ævar Arnfjörð BjarmasonFeb 16, 2022
  6. Elijah NewrenFeb 16, 2022
  7. js/apply-partial-clone-filters-recursively (Was: Re: What's cooking in git.git (Feb 2022, #04; Tue, 15))Elijah Newren, Feb 16, 2022
  8. ds/sparse-checkout-requires-per-worktree-config (Was: Re: What's cooking in git.git (Feb 2022, #04; Tue, 15))Elijah Newren, Feb 16, 2022
  9. Derrick StoleeFeb 16, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.