]> git.ipfire.org Git - thirdparty/git.git/commit - repo-settings.c
fetch: add fetch.writeCommitGraph config setting
authorDerrick Stolee <dstolee@microsoft.com>
Tue, 3 Sep 2019 02:22:02 +0000 (19:22 -0700)
committerJunio C Hamano <gitster@pobox.com>
Tue, 3 Sep 2019 19:06:14 +0000 (12:06 -0700)
commit50f26bd035816c2bb79582b834d59b49292502a9
tree48d8a75a581c0acb513b5351f472d0a6aa97fe93
parentaaf633c2ad10b47af7623c130ddfe7231658c7e4
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>
Documentation/config/feature.txt
Documentation/config/fetch.txt
builtin/fetch.c
repo-settings.c
repository.h
t/t5510-fetch.sh