diff options
| author | Joey Hess <joeyh@joeyh.name> | 2021-11-19 11:53:25 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2021-11-19 12:00:39 -0400 |
| commit | 15d617f7e117daf7647d35735c1dc10b6803f78f (patch) | |
| tree | 22482faa9965836206b61f3ab0add747df50168d /Types/Concurrency.hs | |
| parent | 261947683b27baaf61667e7c50f215c0c7fd4c89 (diff) | |
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.
Diffstat (limited to 'Types/Concurrency.hs')
| -rw-r--r-- | Types/Concurrency.hs | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/Types/Concurrency.hs b/Types/Concurrency.hs index ccab1ee0a9..9204f1d0f4 100644 --- a/Types/Concurrency.hs +++ b/Types/Concurrency.hs @@ -22,3 +22,4 @@ parseConcurrency s = Concurrent <$> readish s data ConcurrencySetting = ConcurrencyCmdLine Concurrency | ConcurrencyGitConfig Concurrency + deriving (Eq) |