From 4f3fb34844eef457d910fbbb78fe676f696eeac5 Mon Sep 17 00:00:00 2001
From: Eelco Dolstra <edolstra@gmail.com>
Date: Mon, 27 Feb 2017 15:58:24 +0100
Subject: [PATCH] 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.)
---
 doc/manual/release-notes/rl-1.8.xml | 4 ++--
 1 file 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
-- 
GitLab