From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Thu, 9 May 2024 18:46:57 +0000 (-0400)
Subject: Merge "2.13: Cleanup duplicate paragraph"
X-Git-Url: https://git.liburcu.org/?a=commitdiff_plain;h=HEAD;hp=-c;p=lttng-docs.git

Merge "2.13: Cleanup duplicate paragraph"
---

c96644bd343e27a9fe956642845b35a630ce97f6
diff --combined 2.13/lttng-docs-2.13.txt
index fcc83a2,680bb67..d395290
--- a/2.13/lttng-docs-2.13.txt
+++ b/2.13/lttng-docs-2.13.txt
@@@ -1236,7 -1236,7 +1236,7 @@@ Once you have completed the <<tracing-t
  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,6 -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
@@@ -1876,10 -1881,6 +1876,6 @@@ consumes the marked sub-buffer, which r
  {note-no-anim}
  ====
  
- In an ideal world, sub-buffers are consumed faster than they're filled.
- In the real world, however, all sub-buffers can be full at some point,
- leaving no space to record the following events.
- 
  In an ideal world, sub-buffers are consumed faster than they're filled,
  as it's the case in the previous animation. In the real world,
  however, all sub-buffers can be full at some point, leaving no space to
@@@ -7967,8 -7968,9 +7963,8 @@@ The LTTng kernel and user space tracer
  
  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
@@@ -8926,6 -8928,11 +8922,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.