2.12, 2.13: Remove mentions of lttng-analysis

LTTng-analyses has now been archived for some time and is no longer
supported in any fashion.

Change-Id: Ide211eeffa4593fd378c0f5d01de1ae52748fe21
Signed-off-by: Kienan Stewart <kstewart@efficios.com>

diff --git a/2.12/lttng-docs-2.12.txt b/2.12/lttng-docs-2.12.txt
index c3a937d05c85ccf62d9a7eaa952dddc0d993f850..5c1cce63fe130568c80e20fa6cff545f36e7a285 100644 (file)
--- a/2.12/lttng-docs-2.12.txt
+++ b/2.12/lttng-docs-2.12.txt
@@ -1114,7 +1114,7 @@ Once you have completed the <<tracing-the-linux-kernel,Trace the Linux
 kernel>> and <<tracing-your-own-user-application,Trace a user
 application>> tutorials, you can inspect the recorded events.
 
-There are many tools you can use to read LTTng traces:
+There are tools you can use to read LTTng traces:
 
 https://babeltrace.org/[Babeltrace{nbsp}2]::
     A rich, flexible trace manipulation toolkit which includes
@@ -1134,11 +1134,6 @@ http://tracecompass.org/[Trace Compass]::
     A graphical user interface for viewing and analyzing any type of
     logs or traces, including those of LTTng.
 
-https://github.com/lttng/lttng-analyses[**LTTng analyses**]::
-    An experimental project which includes many high-level analyses of
-    LTTng kernel traces, like scheduling statistics, interrupt
-    frequency distribution, top CPU usage, and more.
-
 NOTE: This section assumes that LTTng saved the traces it recorded
 during the previous tutorials to their default location, in the
 dir:{$LTTNG_HOME/lttng-traces} directory. The env:LTTNG_HOME
@@ -8061,11 +8056,6 @@ log level::
   project which you can use to send and receive control messages to and
   from a <<def-session-daemon,session daemon>>.
 
-LTTng analyses::
-  The https://github.com/lttng/lttng-analyses[LTTng analyses] project,
-  which is a set of analyzing programs that you can use to obtain a
-  higher level view of an <<def-lttng,LTTng>> <<def-trace,trace>>.
-
 cmd:lttng-consumerd::
   The name of the <<def-consumer-daemon,consumer daemon>> program.
 

diff --git a/2.13/lttng-docs-2.13.txt b/2.13/lttng-docs-2.13.txt
index 3349d481df92f99698607130910fb897b60ad348..fcc83a2ed9b4c4a018c6ec16dbec6318f5f2c4cf 100644 (file)
--- a/2.13/lttng-docs-2.13.txt
+++ b/2.13/lttng-docs-2.13.txt
@@ -1236,7 +1236,7 @@ Once you have completed the <<tracing-the-linux-kernel,Record Linux
 kernel events>> and <<tracing-your-own-user-application,Record user
 application events>> tutorials, you can inspect the recorded events.
 
-There are many tools you can use to read LTTng traces:
+There are tools you can use to read LTTng traces:
 
 https://babeltrace.org/[Babeltrace{nbsp}2]::
     A rich, flexible trace manipulation toolkit which includes
@@ -1255,11 +1255,6 @@ http://tracecompass.org/[Trace Compass]::
     A graphical user interface for viewing and analyzing any type of
     logs or traces, including those of LTTng.
 
-https://github.com/lttng/lttng-analyses[LTTng analyses]::
-    An experimental project which includes many high-level analyses of
-    LTTng kernel traces, like scheduling statistics, interrupt
-    frequency distribution, top CPU usage, and more.
-
 NOTE: This section assumes that LTTng wrote the traces it recorded
 during the previous tutorials to their default location, in the
 dir:{$LTTNG_HOME/lttng-traces} directory. The env:LTTNG_HOME
@@ -7972,9 +7967,8 @@ The LTTng kernel and user space tracers generate state dump
 
 An analysis can use the state dump event records to set an initial state
 before it builds the rest of the state from the subsequent event
-records. http://tracecompass.org/[Trace Compass] and
-https://github.com/lttng/lttng-analyses[LTTng analyses] are notable
-examples of applications which use the state dump of an LTTng trace.
+records. http://tracecompass.org/[Trace Compass] is a notable
+example of an application which uses the state dump of an LTTng trace.
 
 When you <<taking-a-snapshot,take a snapshot>>, it's possible that the
 state dump event records aren't included in the snapshot trace files
@@ -8932,11 +8926,6 @@ log level::
   project which you can use to send and receive control messages to and
   from a <<def-session-daemon,session daemon>>.
 
-LTTng analyses::
-  The https://github.com/lttng/lttng-analyses[LTTng analyses] project,
-  which is a set of analyzing programs that you can use to obtain a
-  higher level view of an <<def-lttng,LTTng>> <<def-trace,trace>>.
-
 cmd:lttng-consumerd::
   The name of the <<def-consumer-daemon,consumer daemon>> program.