Re: What's cooking in git.git (Mar 2020, #09; Sun, 29)

> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.  The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
> 
> You can find the changes described here in the integration branches
> of the repositories listed at
> 
>     http://git-blame.blogspot.com/p/git-public-repositories.html
> --------------------------------------------------
> [Stalled]
> 
> * gs/commit-graph-path-filter (2020-02-12) 12 commits
>  - (bytesex breakage band-aid)
>  - 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.
> 
>  Expecting a reroll.
>  cf. <fdcbd793-57c2-f5ea-ccb9-cf34e911b669@gmail.com>
>  Breakage due to byte-order dependency reported.
>