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: Re: What's cooking in git.git (Apr 2018, #01; Mon, 9)
Date: Mon, 9 Apr 2018 09:37:11 -0400	[thread overview]
Message-ID: <98394864-ece6-5112-0274-b2399087f207@gmail.com> (raw)
In-Reply-To: <xmqqd0z865pk.fsf@gitster-ct.c.googlers.com>

On 4/9/2018 6:21 AM, Junio C Hamano wrote:
> * ds/commit-graph (2018-04-02) 16 commits
>   - commit-graph: implement "--additive" option
>   - 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 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
>   - csum-file: refactor finalize_hashfile() method
>   - csum-file: rename hashclose() to finalize_hashfile()
>   - Merge branch 'jk/cached-commit-buffer' into HEAD
>   - Merge branch 'jt/binsearch-with-fanout' into HEAD
>   (this branch is used by ds/lazy-load-trees.)
>
>   Precompute and store information necessary for ancestry traversal
>   in a separate file to optimize graph walking.
>
>   Ready???
>   It seems that this topic is getting there.

I think this patch is ready to go, barring the edit of "--additive" to 
"--append" in the final commit message and squashing following diff into 
"commit-graph: implement git commit-graph read":

@@ -31,7 +31,7 @@ static struct opts_commit_graph {

  static int graph_read(int argc, const char **argv)
  {
-       struct commit_graph *graph = 0;
+       struct commit_graph *graph = NULL;
         char *graph_name;

         static struct option builtin_commit_graph_read_options[] = {

If you prefer that I re-roll with those changes, I can send a v8.

I'm currently working on new series based on this feature:

* [1] Lazy-load trees when reading commit-graph (ds/lazy-load-trees)

* [2] Compute and consume generation numbers

* Move commit-graph.c globals to the_repository

* Implement 'fsck' functionality for the commit-graph file

* Integrate 'commit-graph write' into 'gc --auto'

I would also like to open the feature to other contributors, especially 
for others who can contribute performance improvements using generation 
numbers. We had a very valuable discussion on the list [2], and I look 
forward to more collaborations like that.

Thanks,
-Stolee

[1] 
https://public-inbox.org/git/20180403120057.173849-1-dstolee@microsoft.com/T/#u

[2] 
https://public-inbox.org/git/20180403165143.80661-1-dstolee@microsoft.com/T/#u

  reply	other threads:[~2018-04-09 13:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 10:21 What's cooking in git.git (Apr 2018, #01; Mon, 9) Junio C Hamano
2018-04-09 13:37 ` Derrick Stolee [this message]
2018-04-09 16:49   ` Ramsay Jones
2018-04-09 22:08     ` Junio C Hamano
2018-04-10 12:57       ` Derrick Stolee
2018-04-10 19:12         ` Stefan Beller
2018-04-10 19:21         ` Ramsay Jones
2018-04-10 19:21           ` Ramsay Jones
2018-04-10 19:35           ` Derrick Stolee
2018-04-10 20:22             ` Ramsay Jones
2018-04-10 20:37               ` Ramsay Jones
2018-04-10 21:46         ` Junio C Hamano
2018-04-09 15:31 ` Duy Nguyen
2018-04-09 17:23   ` Stefan Beller
2018-04-09 20:14 ` Johannes Schindelin
2018-04-09 21:32   ` Johannes Schindelin
2018-04-10 12:25 ` Johannes Schindelin
2018-04-10 21:02 ` git-gui branches, was " Johannes Schindelin
2018-04-10 21:38   ` Junio C Hamano
2018-04-10 21:54     ` Stefan Beller
2018-04-10 22:41     ` Johannes Schindelin
2018-04-11 10:13 ` Phillip Wood
2018-04-11 18:47 ` Jakub Narebski
2018-04-11 20:51   ` Ævar Arnfjörð Bjarmason

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=98394864-ece6-5112-0274-b2399087f207@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).