diff options
| author | Eelco Dolstra <edolstra@gmail.com> | 2017-02-27 15:58:24 +0100 |
|---|---|---|
| committer | Eelco Dolstra <edolstra@gmail.com> | 2017-02-27 15:58:24 +0100 |
| commit | 4f3fb34844eef457d910fbbb78fe676f696eeac5 (patch) | |
| tree | 8b8491181cc500512ae0aef848249abe5949ff38 | |
| parent | 3cb0387d3f0932c9ce6f0aca2663860da7a65fb0 (diff) | |
Fix 1.8 release note about build-max-jobs
We set build-cores automatically, not build-max-jobs. (The commit
message for de4cdd0d47adc70a4db12397a42c18ee50b4e662 also got this
wrong.)
| -rw-r--r-- | doc/manual/release-notes/rl-1.8.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/release-notes/rl-1.8.xml b/doc/manual/release-notes/rl-1.8.xml index 48caac2c6..c854c5c5f 100644 --- a/doc/manual/release-notes/rl-1.8.xml +++ b/doc/manual/release-notes/rl-1.8.xml @@ -83,8 +83,8 @@ $ nix-store -l $(which xterm) caches).</para></listitem> <listitem><para>The configuration option - <option>build-max-jobs</option> now defaults to the number of - available CPU cores.</para></listitem> + <option>build-cores</option> now defaults to the number of available + CPU cores.</para></listitem> <listitem><para>Build users are now used by default when Nix is invoked as root. This prevents builds from accidentally running as |