aboutsummaryrefslogtreecommitdiff
path: root/doc/manual
diff options
context:
space:
mode:
Diffstat (limited to 'doc/manual')
-rw-r--r--doc/manual/command-ref/conf-file.xml10
-rw-r--r--doc/manual/command-ref/opt-common-syn.xml1
-rw-r--r--doc/manual/command-ref/opt-common.xml55
3 files changed, 0 insertions, 66 deletions
diff --git a/doc/manual/command-ref/conf-file.xml b/doc/manual/command-ref/conf-file.xml
index 598b15827..4c8f3d9d3 100644
--- a/doc/manual/command-ref/conf-file.xml
+++ b/doc/manual/command-ref/conf-file.xml
@@ -406,16 +406,6 @@ flag, e.g. <literal>--option gc-keep-outputs false</literal>.</para>
</varlistentry>
- <varlistentry><term><literal>binary-cache-secret-key-file</literal></term>
-
- <listitem><para>Path of the file containing the secret key to be
- used for signing binary caches. This file can be generated using
- <command>nix-store
- --generate-binary-cache-key</command>.</para></listitem>
-
- </varlistentry>
-
-
<varlistentry><term><literal>binary-caches-parallel-connections</literal></term>
<listitem><para>The maximum number of parallel HTTP connections
diff --git a/doc/manual/command-ref/opt-common-syn.xml b/doc/manual/command-ref/opt-common-syn.xml
index d65f4009e..5b7936393 100644
--- a/doc/manual/command-ref/opt-common-syn.xml
+++ b/doc/manual/command-ref/opt-common-syn.xml
@@ -31,7 +31,6 @@
<arg><option>-K</option></arg>
<arg><option>--fallback</option></arg>
<arg><option>--readonly-mode</option></arg>
-<arg><option>--log-type</option> <replaceable>type</replaceable></arg>
<arg><option>--show-trace</option></arg>
<arg>
<option>-I</option>
diff --git a/doc/manual/command-ref/opt-common.xml b/doc/manual/command-ref/opt-common.xml
index c7e8ae1ed..bc26a9061 100644
--- a/doc/manual/command-ref/opt-common.xml
+++ b/doc/manual/command-ref/opt-common.xml
@@ -201,61 +201,6 @@
</varlistentry>
-<varlistentry xml:id="opt-log-type"><term><option>--log-type</option>
-<replaceable>type</replaceable></term>
-
- <listitem>
-
- <para>This option determines how the output written to standard
- error is formatted. Nix’s diagnostic messages are typically
- <emphasis>nested</emphasis>. For instance, when tracing Nix
- expression evaluation (<command>nix-env -vvvvv</command>, messages
- from subexpressions are nested inside their parent expressions. Nix
- builder output is also often nested. For instance, the Nix Packages
- generic builder nests the various build tasks (unpack, configure,
- compile, etc.), and the GNU Make in <literal>stdenv-linux</literal>
- has been patched to provide nesting for recursive Make
- invocations.</para>
-
- <para><replaceable>type</replaceable> can be one of the
- following:
-
- <variablelist>
-
- <varlistentry><term><literal>pretty</literal></term>
-
- <listitem><para>Pretty-print the output, indicating different
- nesting levels using spaces. This is the
- default.</para></listitem>
-
- </varlistentry>
-
- <varlistentry><term><literal>escapes</literal></term>
-
- <listitem><para>Indicate nesting using escape codes that can be
- interpreted by the <command>nix-log2xml</command> tool in the
- Nix source distribution. The resulting XML file can be fed into
- the <command>log2html.xsl</command> stylesheet to create an HTML
- file that can be browsed interactively, using JavaScript to
- expand and collapse parts of the output.</para></listitem>
-
- </varlistentry>
-
- <varlistentry><term><literal>flat</literal></term>
-
- <listitem><para>Remove all nesting.</para></listitem>
-
- </varlistentry>
-
- </variablelist>
-
- </para>
-
- </listitem>
-
-</varlistentry>
-
-
<varlistentry><term><option>--arg</option> <replaceable>name</replaceable> <replaceable>value</replaceable></term>
<listitem><para>This option is accepted by