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

tb/pack-revindex-on-disk (was: Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))

From
Taylor Blau <me@ttaylorr.com>
Date
Apr 18, 2023, 14:53 UTC
Message-ID
<ZD6u24OqvgoeIcBl@nand.local>
In-Reply-To
<xmqqfs8xfw25.fsf@gitster.g>
On Tue, Apr 18, 2023 at 01:12:34AM -0700, Junio C Hamano wrote:
Show 16 quoted lines
> * tb/pack-revindex-on-disk (2023-04-13) 7 commits
>  - t: invert `GIT_TEST_WRITE_REV_INDEX`
>  - config: enable `pack.writeReverseIndex` by default
>  - pack-revindex: introduce `pack.readReverseIndex`
>  - pack-revindex: introduce GIT_TEST_REV_INDEX_DIE_ON_DISK
>  - pack-revindex: make `load_pack_revindex` take a repository
>  - t5325: mark as leak-free
>  - pack-write.c: plug a leak in stage_tmp_packfiles()
>  (this branch is used by ds/fsck-pack-revindex.)
>
>  The on-disk reverse index that allows mapping from the pack offset
>  to the object name for the object stored at the offset has been
>  enabled by default.
>
>  Will merge to 'next'?
>  source: <cover.1681338013.git.me@ttaylorr.com>

Yeah, this one has been reviewed thoroughly by Stolee. We made some minor tweaks in v2, which he reviewed and said were ready to merge.

Thanks, Taylor

Previous: Junio C HamanoNext: Taylor Blau
Message 2 of 8 in “What's cooking in git.git (Apr 2023, #05; Mon, 17)”
  1. Junio C HamanoApr 18, 2023
  2. tb/pack-revindex-on-disk (was: Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))Taylor Blau, Apr 18, 2023
  3. tb/enable-cruft-packs-by-default (was: Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))Taylor Blau, Apr 18, 2023
  4. tb/ban-strtok (was: Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))Taylor Blau, Apr 18, 2023
  5. Junio C HamanoApr 18, 2023
  6. Taylor BlauApr 18, 2023
  7. en/header-split-cache-h (Was Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))Elijah Newren, Apr 19, 2023
  8. rj/branch-unborn-in-other-worktrees (was Re: What's cooking in git.git (Apr 2023, #05; Mon, 17))Rubén Justo, Apr 19, 2023

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.