Derrick Stolee <stolee@xxxxxxxxx> writes: > The reason to use RUN_SETUP_GENTLY was probably due to some thought > of modifying the background maintenance schedule without being in a > Git repository. However, we currently run the [un]register logic > inside of the stop|start subcommands, so a GIT_DIR is required there, > too. Meaning all the operations we currently support requires to be done in a repository? If so, that may be acceptable. When a new operation that does not require to be in a repository is added, or when an existing operation is updated not to require to be in a repository, reverting the change and then checking in the implementation of each operation if we are in a repository instead should be easy enough---it pretty much should amount to Rafael's patch, right? But then, being prepared for that future already is also OK, so I can go either way. Please figure it out between you ;-) Thanks, all.
