Re: What's cooking in git.git (May 2020, #05; Thu, 14)

From: Derrick Stolee <stolee@gmail.com>
Date: May 15, 2020, 10:16 UTC
Message-ID: <74397ce4-be15-51e8-fb28-81eafdca792c@gmail.com>
In-Reply-To: <xmqqpnb6nk7x.fsf@gitster.c.googlers.com>

On 5/14/2020 7:57 PM, Junio C Hamano wrote:

Show 16 quoted lines

> --------------------------------------------------
> [Graduated to "master"]
> 
> * ds/bloom-cleanup (2020-05-11) 7 commits
>   (merged to 'next' on 2020-05-11 at 046d49d455)
>  + completion: offer '--(no-)patch' among 'git log' options
>  + bloom: use num_changes not nr for limit detection
>  + bloom: de-duplicate directory entries
>  + Documentation: changed-path Bloom filters use byte words
>  + bloom: parse commit before computing filters
>  + test-bloom: fix usage typo
>  + bloom: fix whitespace around tab length
> 
>  Code cleanup and typofixes.
>  This is an early part of ds/line-log-on-bloom that has been cooking
>  in 'next'.

Thanks for taking the time to merge this portion for the release candidate.

Show 12 quoted lines

> * ds/line-log-on-bloom (2020-05-11) 5 commits
>   (merged to 'next' on 2020-05-11 at 046d49d455)
>  + line-log: integrate with changed-path Bloom filters
>  + line-log: try to use generation number-based topo-ordering
>  + line-log: more responsive, incremental 'git log -L'
>  + t4211-line-log: add tests for parent oids
>  + line-log: remove unused fields from 'struct line_log_data'
> 
>  "git log -L..." now takes advantage of the "which paths are touched
>  by this commit?" info stored in the commit-graph system.
> 
>  Will cook in 'next'.

Good plan. This can wait until after the release.

Thanks, -Stolee