diff options
| author | Vagrant Cascadian <vagrant@debian.org> | 2019-05-22 16:04:46 -0700 |
|---|---|---|
| committer | Vagrant Cascadian <vagrant@debian.org> | 2019-05-22 18:21:11 -0700 |
| commit | f457397ad76eb752a990eefd4b90681fc136d14a (patch) | |
| tree | 0c3d00b714757e33e3d97399641e7738d263baaf /gnu/packages | |
| parent | d087a3a6c186beb548649046599e006c233d9561 (diff) | |
| download | patches-f457397ad76eb752a990eefd4b90681fc136d14a.tar patches-f457397ad76eb752a990eefd4b90681fc136d14a.tar.gz | |
gnu: stress-make: Fix typo "explicitly".
* gnu/packages/debug (stress-make)[description]: Fix typo.
Diffstat (limited to 'gnu/packages')
| -rw-r--r-- | gnu/packages/debug.scm | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/gnu/packages/debug.scm b/gnu/packages/debug.scm index b035951e26..e199e859ff 100644 --- a/gnu/packages/debug.scm +++ b/gnu/packages/debug.scm @@ -313,7 +313,7 @@ down the road.") (home-page "https://github.com/losalamos/stress-make") (synopsis "Expose race conditions in Makefiles") (description - "Stress Make is a customized GNU Make that explicitely manages the order + "Stress Make is a customized GNU Make that explicitly manages the order in which concurrent jobs are run to provoke erroneous behavior into becoming manifest. It can run jobs in the order in which they're launched, in backwards order, or in random order. The thought is that if code builds correctly with |