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

Re: What's cooking in git.git (Feb 2020, #02; Mon, 10)

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 11, 2020, 20:56 UTC
Message-ID
<xmqqtv3wvo5c.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<819852c9-68dc-11e3-d81d-ddd216953d72@gmail.com>
Garima Singh <garimasigit@gmail.com> writes:
Show 33 quoted lines
> On 2/10/2020 5:31 PM, Junio C Hamano wrote:
>
>> * gs/commit-graph-path-filter (2020-02-06) 11 commits
>>  - commit-graph: add GIT_TEST_COMMIT_GRAPH_CHANGED_PATHS test flag
>>  - revision.c: use Bloom filters to speed up path based revision walks
>>  - commit-graph: add --changed-paths option to write subcommand
>>  - commit-graph: reuse existing Bloom filters during write.
>>  - commit-graph: write Bloom filters to commit graph file
>>  - commit-graph: examine commits by generation number
>>  - commit-graph: examine changed-path objects in pack order
>>  - commit-graph: compute Bloom filters for changed paths
>>  - diff: halt tree-diff early after max_changes
>>  - bloom: core Bloom filter implementation for changed paths
>>  - commit-graph: use MAX_NUM_CHUNKS
>> 
>>  Introduce an extension to the commit-graph to make it efficient to
>>  check for the paths that were modified at each commit using Bloom
>>  filters.
>> 
>>  Breakage due to byte-order dependency reported.
>> 
>
> Hey Junio! 
>
> We fixed the byte-order dependency bug in the patch I just sent out 
> here: 
>  https://lore.kernel.org/git/ba856e20-0a3c-e2d2-6744-b9abfacdc465@gmail.com/
>
> I am squashing this patch into the appropriate commits in v3, which I will 
> send out after people have had a chance to complete their review of v2. 
>
> Could you please apply that patch on top of the pu branch 
> gs/commit-graph-path-filter so that it also has the fix? 

Can you fix that in place? The topic is not in 'next' yet, so we do not have to go incremental and apply an "oops, this on top will fix all the gotchas in earlier steps" band-aid.

Thanks.
Previous: Garima SinghNext: Junio C Hamano
Message 4 of 5 in “What's cooking in git.git (Feb 2020, #02; Mon, 10)”
  1. Junio C HamanoFeb 10, 2020
  2. ds/ (was Re: What's cooking in git.git (Feb 2020, #02; Mon, 10))Derrick Stolee, Feb 11, 2020
  3. Garima SinghFeb 11, 2020
  4. Junio C HamanoFeb 11, 2020
  5. Junio C HamanoFeb 11, 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.