From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2021, #04; Tue, 10)
Date: Wed, 11 Aug 2021 14:21:04 +0200 [thread overview]
Message-ID: <YRPAsJSfVbNmYh3v@ncase> (raw)
In-Reply-To: <xmqqh7fwbx86.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
On Tue, Aug 10, 2021 at 06:12:41PM -0700, Junio C Hamano wrote:
[snip]
> * 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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-08-11 12:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-11 1:12 What's cooking in git.git (Aug 2021, #04; Tue, 10) Junio C Hamano
2021-08-11 1:34 ` brian m. carlson
2021-08-11 7:22 ` Fabian Stelzer
2021-08-11 8:04 ` Carlo Marcelo Arenas Belón
2021-08-11 16:13 ` Junio C Hamano
2021-08-11 9:51 ` Phillip Wood
2021-08-11 16:19 ` Junio C Hamano
2021-08-13 8:10 ` ZheNing Hu
2021-08-11 10:45 ` Atharva Raykar
2021-08-11 17:30 ` Junio C Hamano
2021-08-11 12:21 ` Patrick Steinhardt [this message]
2021-08-11 16:44 ` Junio C Hamano
2021-08-11 17:49 ` David Turner
2021-08-11 19:00 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YRPAsJSfVbNmYh3v@ncase \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.