summaryrefslogtreecommitdiff
path: root/t/t4013/diff.whatchanged_--root_master
diff options
context:
space:
mode:
authorLibravatar Derrick Stolee <dstolee@microsoft.com>2019-09-02 19:22:02 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2019-09-03 12:06:14 -0700
commit50f26bd035816c2bb79582b834d59b49292502a9 (patch)
tree48d8a75a581c0acb513b5351f472d0a6aa97fe93 /t/t4013/diff.whatchanged_--root_master
parentrepo-settings: create feature.experimental setting (diff)
downloadtgif-50f26bd035816c2bb79582b834d59b49292502a9.tar.xz
fetch: add fetch.writeCommitGraph config setting
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. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4013/diff.whatchanged_--root_master')
0 files changed, 0 insertions, 0 deletions