have setConcurrency stop any running git coprocesses

When non-concurrent git coprocesses have been started, setConcurrency
used to not stop them, and so could leak processes when enabling
concurrency, eg when forkState is called.

I do not think that ever actually happened, given where setConcurrency
is called. And it probably would only leak one of each process, since it
never downgrades from concurrent to non-concurrent.
This commit is contained in:
Joey Hess 2021-11-19 11:53:25 -04:00
parent 261947683b
commit 15d617f7e1
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
3 changed files with 39 additions and 12 deletions

View file

@ -22,3 +22,4 @@ parseConcurrency s = Concurrent <$> readish s
data ConcurrencySetting
= ConcurrencyCmdLine Concurrency
| ConcurrencyGitConfig Concurrency
deriving (Eq)