Re: What's cooking in git.git (Aug 2021, #04; Tue, 10)

From: Patrick Steinhardt <ps@pks.im>
Date: Aug 11, 2021, 12:21 UTC
Message-ID: <YRPAsJSfVbNmYh3v@ncase>
In-Reply-To: <xmqqh7fwbx86.fsf@gitster.g>

On Tue, Aug 10, 2021 at 06:12:41PM -0700, Junio C Hamano wrote: [snip]

Show 19 quoted lines

> * ps/fetch-pack-load-refs-optim (2021-08-04) 1 commit
>   (merged to 'next' on 2021-08-09 at 4744a01fd5)
>  + fetch-pack: speed up loading of refs via commit graph
> 
>  Loading of ref tips to prepare for common ancestry negotiation in
>  "git fetch-pack" has been optimized by taking advantage of the
>  commit graph when available.
> 
>  Will cook in 'next'.
> 
> 
> * ps/connectivity-optim (2021-08-09) 5 commits
>  - revision: avoid hitting packfiles when commits are in commit-graph
>  - commit-graph: split out function to search commit position
>  - revision: stop retrieving reference twice
>  - connected: do not sort input revisions
>  - revision: separate walk and unsorted flags
> 
>  The revision traversal API has been optimized by taking advanrage

These descriptions end up in the release notes, right? If so:

    s/advanrage/advantage/

>  of the commit-graph, when available, to determine if a commit is
>  reachable from any of the existing refs.
> 
>  Will merge to 'next'.

Thanks for both!

Patrick