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

Re: sg/commit-graph-cleanups (was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6))

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 7, 2020, 15:12 UTC
Message-ID
<xmqqzh8b5pgv.fsf@gitster.c.googlers.com>
In-Reply-To
<90cf9ac2-1ab0-1c9b-706b-6c5176ab47dd@gmail.com>
Derrick Stolee <stolee@gmail.com> writes:
Show 44 quoted lines
> On 7/7/2020 1:57 AM, Junio C Hamano wrote:
>> * ds/commit-graph-bloom-updates (2020-07-01) 10 commits
>>   (merged to 'next' on 2020-07-06 at 177e6b362e)
>>  + commit-graph: check all leading directories in changed path Bloom filters
>>  + revision: empty pathspecs should not use Bloom filters
>>  + revision.c: fix whitespace
>>  + commit-graph: check chunk sizes after writing
>>  + commit-graph: simplify chunk writes into loop
>>  + commit-graph: unify the signatures of all write_graph_chunk_*() functions
>>  + commit-graph: persist existence of changed-paths
>>  + bloom: fix logic in get_bloom_filter()
>>  + commit-graph: change test to die on parse, not load
>>  + commit-graph: place bloom_settings in context
>>  (this branch uses sg/commit-graph-cleanups.)
>> 
>>  Updates to the changed-paths bloom filter.
>> 
>>  Will merge to 'master'.
>> 
>> * sg/commit-graph-cleanups (2020-06-08) 10 commits
>>  + commit-graph: simplify write_commit_graph_file() #2
>>  + commit-graph: simplify write_commit_graph_file() #1
>>  + commit-graph: simplify parse_commit_graph() #2
>>  + commit-graph: simplify parse_commit_graph() #1
>>  + commit-graph: clean up #includes
>>  + diff.h: drop diff_tree_oid() & friends' return value
>>  + commit-slab: add a function to deep free entries on the slab
>>  + commit-graph-format.txt: all multi-byte numbers are in network byte order
>>  + commit-graph: fix parsing the Chunk Lookup table
>>  + tree-walk.c: don't match submodule entries for 'submod/anything'
>>  (this branch is used by ds/commit-graph-bloom-updates.)
>> 
>>  The changed-path Bloom filter is improved using ideas from an
>>  independent implementation.
>> 
>>  Under review.
>>  cf. <20200627155610.GN2898@szeder.dev>
>>  cf. <20200627163335.GO2898@szeder.dev>
>>  cf. <20200627155348.GM2898@szeder.dev>
>
> I see these are both in 'next' (thanks!).
>
> Perhaps the "Under review" status for sg/commit-graph-cleanups
> should be modified to match ds/commit-graph-bloom-updates?

Oops, I am not sure what happened here. There I thought were issues pointed out at least on the latter series but was I hallucinating?

For now, as -rc0 is so close, I'm tempted to mark both of them to be cooked in 'next' during the rc period.

Thanks.
Previous: Junio C HamanoNext: Derrick Stolee
Message 4 of 15 in “What's cooking in git.git (Jul 2020, #01; Mon, 6)”
  1. Junio C HamanoJul 7, 2020
  2. sg/commit-graph-cleanups (was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6))Derrick Stolee, Jul 7, 2020
  3. Junio C HamanoJul 7, 2020
  4. Junio C HamanoJul 7, 2020
  5. Derrick StoleeJul 7, 2020
  6. Junio C HamanoJul 7, 2020
  7. Taylor BlauJul 7, 2020
  8. SZEDER GáborJul 7, 2020
  9. Junio C HamanoJul 7, 2020
  10. SZEDER GáborJul 10, 2020
  11. Junio C HamanoJul 10, 2020
  12. mr/bisect-in-c-2, was Re: What's cooking in git.git (Jul 2020, #01; Mon, 6)Johannes Schindelin, Jul 8, 2020
  13. Junio C HamanoJul 8, 2020
  14. Junio C HamanoJul 8, 2020
  15. Johannes SchindelinJul 9, 2020

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.