gc: perform incremental repack when implictly enabled
builtin/gc.c has two ways of checking if multi-pack-index is enabled:
- git_config_get_bool() in incremental_repack_auto_condition()
- the_repository->settings.core_multi_pack_index in
maintenance_task_incremental_repack()
The two implementations have existed since the incremental-repack task
was introduced in e841a79a13
(maintenance: add incremental-repack auto
condition, 2020-09-25). These two values can diverge because
prepare_repo_settings() enables the feature in the_repository->settings
by default.
In the case where core.multiPackIndex is not set in the config, the auto
condition would fail, causing the incremental-repack task to not be
run. Because we always want to consider the default values, we should
always use the_repository->settings.
Standardize on using the_repository->settings.core_multi_pack_index to
check if multi-pack-index is enabled.
Signed-off-by: Glen Choo <chooglen@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:

committed by
Junio C Hamano

parent
dc5570872f
commit
a897ab7ed1
@ -1049,12 +1049,11 @@ static int maintenance_task_loose_objects(struct maintenance_run_opts *opts)
|
||||
static int incremental_repack_auto_condition(void)
|
||||
{
|
||||
struct packed_git *p;
|
||||
int enabled;
|
||||
int incremental_repack_auto_limit = 10;
|
||||
int count = 0;
|
||||
|
||||
if (git_config_get_bool("core.multiPackIndex", &enabled) ||
|
||||
!enabled)
|
||||
prepare_repo_settings(the_repository);
|
||||
if (!the_repository->settings.core_multi_pack_index)
|
||||
return 0;
|
||||
|
||||
git_config_get_int("maintenance.incremental-repack.auto",
|
||||
|
Reference in New Issue
Block a user