"Matthew John Cheetham via GitGitGadget" <gitgitgadget@xxxxxxxxx>
writes:
> +static int start_fsmonitor_daemon(void)
> +{
> + assert(fsmonitor_ipc__is_supported());
> +
> + if (fsmonitor_ipc__get_state() != IPC_STATE__LISTENING)
> + return run_git("fsmonitor--daemon", "start", NULL);
> +
> + return 0;
> +}
The function got ultra simple ;-).
> @@ -247,6 +265,9 @@ static int register_dir(void)
> if (toggle_maintenance(1))
> return error(_("could not turn on maintenance"));
>
> + if (fsmonitor_ipc__is_supported() && start_fsmonitor_daemon())
> + return error(_("could not start the FSMonitor daemon"));
> +
> return 0;
> }
As long as it is done consistently, I do not think it makes a huge
difference between the "call it only when supported" and "when asked
to do what we do not support, silently succeed without doing
anything". It however makes the code appear to be more in control
to do it this way, I think, which is good.
