summaryrefslogtreecommitdiff
path: root/builtin/fetch.c
diff options
context:
space:
mode:
authorDerrick Stolee <dstolee@microsoft.com>2020-09-17 18:11:51 (GMT)
committerJunio C Hamano <gitster@pobox.com>2020-09-17 18:30:05 (GMT)
commit4ddc79b2dac18189e7ff18e99a6fabdd161f866c (patch)
tree5da745e39a69609e31342ea49c4b9bb4412387af /builtin/fetch.c
parent916d0626c202c18e6d615abb69ba1f15b335c3ea (diff)
downloadgit-4ddc79b2dac18189e7ff18e99a6fabdd161f866c.zip
git-4ddc79b2dac18189e7ff18e99a6fabdd161f866c.tar.gz
git-4ddc79b2dac18189e7ff18e99a6fabdd161f866c.tar.bz2
maintenance: add auto condition for commit-graph task
Instead of writing a new commit-graph in every 'git maintenance run --auto' process (when maintenance.commit-graph.enalbed is configured to be true), only write when there are "enough" commits not in a commit-graph file. This count is controlled by the maintenance.commit-graph.auto config option. To compute the count, use a depth-first search starting at each ref, and leaving markers using the SEEN flag. If this count reaches the limit, then terminate early and start the task. Otherwise, this operation will peel every ref and parse the commit it points to. If these are all in the commit-graph, then this is typically a very fast operation. Users with many refs might feel a slow-down, and hence could consider updating their limit to be very small. A negative value will force the step to run every time. Signed-off-by: Derrick Stolee <dstolee@microsoft.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/fetch.c')
0 files changed, 0 insertions, 0 deletions