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:
parent
261947683b
commit
15d617f7e1
3 changed files with 39 additions and 12 deletions
|
@ -22,3 +22,4 @@ parseConcurrency s = Concurrent <$> readish s
|
|||
data ConcurrencySetting
|
||||
= ConcurrencyCmdLine Concurrency
|
||||
| ConcurrencyGitConfig Concurrency
|
||||
deriving (Eq)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue