On 2020-10-01 21:55:40-0400, Derrick Stolee <stolee@xxxxxxxxx> wrote: > On 10/1/2020 8:38 PM, Đoàn Trần Công Danh wrote: > > On 2020-10-01 16:38:48-0400, Derrick Stolee <stolee@xxxxxxxxx> wrote: > >> diff --git a/Documentation/git-maintenance.txt b/Documentation/git-maintenance.txt > >> index 7628a6d157..52fff86844 100644 > >> --- a/Documentation/git-maintenance.txt > >> +++ b/Documentation/git-maintenance.txt > >> @@ -37,6 +37,21 @@ register:: > >> `maintenance.<task>.schedule`. The tasks that are enabled are safe > >> for running in the background without disrupting foreground > >> processes. > >> ++ > >> +If your repository has no `maintenance.<task>.schedule` configuration > >> +values set, then Git will use a recommended default schedule that performs > >> +background maintenance that will not interrupt foreground commands. The > >> +default schedule is as follows: > > > > I don't mind about using a default schedule (but someone else might). > > I think some distributions will be paranoia with this change and shiped > > with disable by default in system config. > > If a user wants to prevent this schedule, then they can simply change > any one of the `.schedule` or `.enabled` configs in their --global config > and these defaults will not be used. > > Of course, perhaps you are missing the fact that "git maintenance run > --schedule=<frequency>" is only run as a cron job if a user chose to > start background maintenance using "git maintenance start" (or "git > maintenance register" after running the 'start' subcommand in another > repo). So this is _not_ starting by default without some amount of > choosing to opt in. Yes, I missed that fact. Sorry for the noise I generated. Thanks, -- Danh
