On Mon, Sep 02, 2019 at 07:22:02PM -0700, Derrick Stolee via GitGitGadget wrote:
> From: Derrick Stolee <dsto...@microsoft.com> > > The commit-graph feature is now on by default, and is being > written during 'git gc' by default. Typically, Git only writes > a commit-graph when a 'git gc --auto' command passes the gc.auto > setting to actualy do work. This means that a commit-graph will > typically fall behind the commits that are being used every day. > > To stay updated with the latest commits, add a step to 'git > fetch' to write a commit-graph after fetching new objects. The > fetch.writeCommitGraph config setting enables writing a split > commit-graph, so on average the cost of writing this file is > very small. Occasionally, the commit-graph chain will collapse > to a single level, and this could be slow for very large repos. > > For additional use, adjust the default to be true when > feature.experimental is enabled. Seems like a good time to do it. We'd eventually want a similar option for updating it on the receiving side of a push, too. I don't insist that come at the same time, but we should at least have a plan about how it will look to the user. Do we want to to have fetch.writeCommitGraph, receive.writeCommitGraph, and then a master transfer.writeCommitGraph? -Peff
