From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2019, #02; Thu, 6)
Date: Wed, 12 Jun 2019 09:19:34 -0400 [thread overview]
Message-ID: <a958e78b-523a-5578-24dc-77597a77c724@gmail.com> (raw)
In-Reply-To: <xmqqimtiqyey.fsf@gitster-ct.c.googlers.com>
On 6/6/2019 3:57 PM, Junio C Hamano wrote:
> * ds/commit-graph-incremental (2019-06-06) 15 commits
> - SQUASH??? 5323 is already taken
> - commit-graph: clean up chains after flattened write
> - commit-graph: verify chains with --shallow mode
> - commit-graph: create options for split files
> - commit-graph: expire commit-graph files
> - commit-graph: allow cross-alternate chains
> - commit-graph: merge commit-graph chains
> - commit-graph: add --split option to builtin
> - commit-graph: write commit-graph chains
> - commit-graph: rearrange chunk count logic
> - commit-graph: add base graphs chunk
> - commit-graph: load commit-graph chains
> - commit-graph: rename commit_compare to oid_compare
> - commit-graph: prepare for commit-graph chains
> - commit-graph: document commit-graph chains
> (this branch uses ds/commit-graph-write-refactor; is tangled with ds/close-object-store.)
Sorry for the tangle here. I'll place the proper use of
close_commit_graph(struct raw_object_store *) into my changes
in the next version.
> * ds/commit-graph-write-refactor (2019-05-13) 11 commits
> - commit-graph: extract write_commit_graph_file()
> - commit-graph: extract copy_oids_to_commits()
> - commit-graph: extract count_distinct_commits()
> - commit-graph: extract fill_oids_from_all_packs()
> - commit-graph: extract fill_oids_from_commit_hex()
> - commit-graph: extract fill_oids_from_packs()
> - commit-graph: create write_commit_graph_context
> - commit-graph: remove Future Work section
> - commit-graph: collapse parameters into flags
> - commit-graph: return with errors during write
> - commit-graph: fix the_repository reference
> (this branch is used by ds/close-object-store and ds/commit-graph-incremental.)
>
> Renamed from commit-graph-format-v2 and changed scope.
>
> Expecting a reroll.
> I think it is almost there, modulo a few internal API details..
You are correct! Sorry for dropping the ball on this, I thought I had
sent an updated version. I will make sure to send an updated series today.
Thanks,
-Stolee
next prev parent reply other threads:[~2019-06-12 13:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 19:57 What's cooking in git.git (Jun 2019, #02; Thu, 6) Junio C Hamano
2019-06-12 9:07 ` Duy Nguyen
2019-06-12 13:19 ` Derrick Stolee [this message]
2019-06-12 17:48 ` 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
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=a958e78b-523a-5578-24dc-77597a77c724@gmail.com \
--to=stolee@gmail.com \
--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.
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).