On 4/6/2020 8:58 PM, Danh Doan wrote: > On 2020-04-06 10:42:23-0400, Derrick Stolee <stolee@xxxxxxxxx> wrote: >> Of course, not every platform has "cron" but that just means we need a >> cross-platform way to launch Git processes on some schedule. That could >> be a command that creates a cron job on platforms that have it, and on > > There's Unix system that doesn't have cron. > People could use other scheduler mechanism. > > A lot of systemd users uses systemd-timer. > I'm using snooze. Thanks for listing some alternatives. I'll look into these. > Each of those set of utilities have different grammar and > configuration. > >> Windows it could create a scheduled task instead. >> 2. "run-on-repos" uses command-line arguments or config to launch "git >> -C <dir> maintenance run" for all configured directories. The >> intention is that this is launched on some schedule by a platform- >> specific scheduling mechanism (i.e. cron). > > So, IIUC, Git will have a _hard_ dependencies on cron on *nix? > Else, we're gonna received a bug-report that some tools doesn't work? No. Such a dependency would be unacceptable. I'm just using cron as an example when available. > I've seen some bug report in our distro that "git add -p" doesn't work > like documented, because it's in "git-perl" packages. > When we merge "git-perl" back to git, other people (who never use > "git add -p" and git-sendemail) complain why does we add a hard dependencies > on perl to git. Good news: "git add -p" is becoming a builtin with a lot of work by some determined contributors. Thanks, -Stolee
