add gitAnnexChildProcess and use instead of incorrect use of runsGitAnnexChildProcess
authorJoey Hess <joeyh@joeyh.name>
Tue, 25 Aug 2020 18:57:25 +0000 (14:57 -0400)
committerJoey Hess <joeyh@joeyh.name>
Tue, 25 Aug 2020 18:57:49 +0000 (14:57 -0400)
commit7bdb0cdc0d6f35d3835e57c3a34740cc98f89719
tree17d9dd67a4cf2f5ddbb118988c60642eb04e066c
parent6b0532e53278bfa992274a4d58fea1eeb671afff
add gitAnnexChildProcess and use instead of incorrect use of runsGitAnnexChildProcess

Fixes reversion in 8.20200617 that made annex.pidlock being enabled result
in some commands stalling, particularly those needing to autoinit.

Renamed runsGitAnnexChildProcess to make clearer where it should be
used.

Arguably, it would be better to have a way to make any process git-annex
runs have the env var set. But then it would need to take the pid lock
when running any and all processes, and that would be a problem when
git-annex runs two processes concurrently. So, I'm left doing it ad-hoc
in places where git-annex really does run a child process, directly
or indirectly via a particular git command.
Annex/GitOverlay.hs
Annex/Init.hs
Annex/Link.hs
Annex/Path.hs
CHANGELOG
Command/Sync.hs
Upgrade.hs
Utility/LockFile/PidLock.hs
doc/bugs/get_is_stuck_unless_a_clone_was_previously_explicitly___34__annex_init__34__ed.mdwn