richardphibel / rpms / systemd

Forked from rpms/systemd 2 years ago
Clone
Blob Blame History Raw
From f29b7bcd85d4e8d824d36fecc130a0d74af718f8 Mon Sep 17 00:00:00 2001
From: David Tardon <dtardon@redhat.com>
Date: Tue, 12 Oct 2021 16:47:48 +0200
Subject: [PATCH] Remove unintended additions to systemd-analyze man page

These changes were introduced in commit
a2e00522971897909db2a81b4daf10e5700f453e .

Resolves: #2004765
---
 man/systemd-analyze.xml | 51 +----------------------------------------
 1 file changed, 1 insertion(+), 50 deletions(-)

diff --git a/man/systemd-analyze.xml b/man/systemd-analyze.xml
index 7c873cbdd1..e17ff0cf90 100644
--- a/man/systemd-analyze.xml
+++ b/man/systemd-analyze.xml
@@ -354,56 +354,7 @@ $ eog targets.svg</programlisting>
       they elapse next. This takes the same input as the <varname>OnCalendar=</varname> setting in
       <citerefentry><refentrytitle>systemd.timer</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
       following the syntax described in
-      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>. By
-      default, only the next time the calendar expression will elapse is shown; use
-      <option>--iterations=</option> to show the specified number of next times the expression
-      elapses.</para>
-
-      <example>
-        <title>Show leap days in the near future</title>
-
-        <programlisting>$ systemd-analyze calendar --iterations=5 '*-2-29 0:0:0'
-  Original form: *-2-29 0:0:0
-Normalized form: *-02-29 00:00:00
-    Next elapse: Sat 2020-02-29 00:00:00 UTC
-       From now: 11 months 15 days left
-       Iter. #2: Thu 2024-02-29 00:00:00 UTC
-       From now: 4 years 11 months left
-       Iter. #3: Tue 2028-02-29 00:00:00 UTC
-       From now: 8 years 11 months left
-       Iter. #4: Sun 2032-02-29 00:00:00 UTC
-       From now: 12 years 11 months left
-       Iter. #5: Fri 2036-02-29 00:00:00 UTC
-       From now: 16 years 11 months left
-</programlisting>
-      </example>
-    </refsect2>
-
-    <refsect2>
-      <title><command>systemd-analyze timespan <replaceable>EXPRESSION</replaceable>...</command></title>
-
-      <para>This command parses a time span and outputs the normalized form and the equivalent value in
-      microseconds. The time span should adhere to the same syntax documented in
-      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
-      Values without associated magnitudes are parsed as seconds.</para>
-
-      <example>
-        <title>Show parsing of timespans</title>
-
-        <programlisting>$ systemd-analyze timespan 1s 300s '1year 0.000001s'
-Original: 1s
-      μs: 1000000
-   Human: 1s
-
-Original: 300s
-      μs: 300000000
-   Human: 5min
-
-Original: 1year 0.000001s
-      μs: 31557600000001
-   Human: 1y 1us
-</programlisting>
-      </example>
+      <citerefentry><refentrytitle>systemd.time</refentrytitle><manvolnum>7</manvolnum></citerefentry>.</para>
     </refsect2>
 
     <refsect2>