From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, dstolee@microsoft.com, sbeller@google.com
Subject: Re: What's cooking in git.git (Mar 2018, #01; Thu, 1)
Date: Fri, 2 Mar 2018 10:14:03 -0500 [thread overview]
Message-ID: <acd10e97-20ad-d04a-a495-0a9223d8b3a2@gmail.com> (raw)
In-Reply-To: <xmqqpo4ne8ud.fsf@gitster-ct.c.googlers.com>
On 3/1/2018 5:20 PM, Junio C Hamano wrote:
> --------------------------------------------------
> [Graduated to "master"]
>
> * jt/binsearch-with-fanout (2018-02-15) 2 commits
> (merged to 'next' on 2018-02-15 at 7648891022)
> + packfile: refactor hash search with fanout table
> + packfile: remove GIT_DEBUG_LOOKUP log statements
> (this branch is used by ds/commit-graph.)
>
> Refactor the code to binary search starting from a fan-out table
> (which is how the packfile is indexed with object names) into a
> reusable helper.
>
> [...]
> --------------------------------------------------
> [New Topics]
>
> * jk/cached-commit-buffer (2018-02-22) 2 commits
> (merged to 'next' on 2018-02-27 at af791d9a1e)
> + revision: drop --show-all option
> + commit: drop uses of get_cached_commit_buffer()
>
> Code clean-up.
>
> Will merge to 'master'.
Thanks! These resolve the dependencies for ds/commit-graph
> * ds/commit-graph (2018-02-20) 13 commits
> - commit-graph: build graph from starting commits
> - commit-graph: read only from specific pack-indexes
> - commit: integrate commit graph with commit parsing
> - commit-graph: close under reachability
> - commit-graph: add core.commitGraph setting
> - commit-graph: implement --delete-expired
> - commit-graph: implement --set-latest
> - commit-graph: implement git commit-graph read
> - commit-graph: implement 'git-commit-graph write'
> - commit-graph: implement write_commit_graph()
> - commit-graph: create git-commit-graph builtin
> - graph: add commit graph design document
> - commit-graph: add format document
>
> Precompute and store information necessary for ancestry traversal
> in a separate file to optimize graph walking.
>
> Reroll exists, but it appears that there will be a further reroll.
> cf. <1519698787-190494-1-git-send-email-dstolee@microsoft.com>
v5 reroll (mentioned above) has limited review, so I won't be rerolling
soon. I'm particularly interested in review on [PATCH 04/13] csum-file:
add CSUM_KEEP_OPEN flag [1].
Thanks,
-Stolee
[1]
https://public-inbox.org/git/1519698787-190494-5-git-send-email-dstolee@microsoft.com/
next prev parent reply other threads:[~2018-03-02 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 22:20 What's cooking in git.git (Mar 2018, #01; Thu, 1) Junio C Hamano
2018-03-02 10:23 ` Luke Diamand
2018-03-02 15:14 ` Derrick Stolee [this message]
2018-03-02 16:33 ` SZEDER Gábor
2018-03-02 17:07 ` Junio C Hamano
2018-03-02 17:11 ` Junio C Hamano
2018-03-02 17:39 ` Lars Schneider
2018-03-02 18:55 ` SZEDER Gábor
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acd10e97-20ad-d04a-a495-0a9223d8b3a2@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).