git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14))
Date: Tue, 18 Jun 2019 09:36:08 -0400	[thread overview]
Message-ID: <8690d49e-31f5-e12a-ae8c-dc217a5476cc@gmail.com> (raw)
In-Reply-To: <xmqqh88ruc1b.fsf@gitster-ct.c.googlers.com>

On 6/14/2019 4:50 PM, Junio C Hamano wrote:
> * ds/commit-graph-incremental (2019-06-12) 16 commits
>  - commit-graph: test --split across alternate without --split
>  - commit-graph: test octopus merges with --split
>  - 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.)
> 
>  The commits in a repository can be described by multiple
>  commit-graph files now, which allows the commit-graph files to be
>  updated incrementally.
> 
>  Will merge to 'next'.

Please hold on this one. I've found multiple issues while integrating
this with VFS for Git and there are enough to merit a full re-roll.
Please ignore the two patches I sent yesterday as I will incorporate them
into the next version of this series.

Thanks,
-Stolee

  parent reply	other threads:[~2019-06-18 13:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 20:50 What's cooking in git.git (Jun 2019, #04; Fri, 14) Junio C Hamano
2019-06-17 17:41 ` js/gcc-8-and-9, was " Johannes Schindelin
2019-06-17 19:54   ` Junio C Hamano
2019-06-18 10:26     ` Johannes Schindelin
2019-06-19 14:28       ` Junio C Hamano
2019-06-17 18:06 ` pw/rebase-abort-clean-rewritten, " Johannes Schindelin
2019-06-17 19:04   ` Phillip Wood
2019-06-18  3:30     ` Junio C Hamano
2019-06-20  9:34       ` Phillip Wood
2019-06-21 13:27         ` Johannes Schindelin
2019-06-17 18:25 ` sg/rebase-progress, " Johannes Schindelin
2019-06-18 13:36 ` Derrick Stolee [this message]
2019-06-19 14:32   ` ds/commit-graph-incremental (was Re: What's cooking in git.git (Jun 2019, #04; Fri, 14)) Junio C Hamano
2019-06-19 14:37     ` Derrick Stolee

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=8690d49e-31f5-e12a-ae8c-dc217a5476cc@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).