lttng/tmf: Minor user and developer guide updates

Change-Id: Ibba6c22d5e39742761ba6b131366ab5686109393
Signed-off-by: Bernd Hufmann <Bernd.Hufmann@ericsson.com>
Reviewed-on: https://git.eclipse.org/r/33851
Tested-by: Hudson CI
Reviewed-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>
Tested-by: Marc-Andre Laperle <marc-andre.laperle@ericsson.com>

diff --git a/org.eclipse.linuxtools.lttng.help/doc/User-Guide.mediawiki b/org.eclipse.linuxtools.lttng.help/doc/User-Guide.mediawiki
index 55602f12d40a7f551f462bf86e2a82be075e0585..8f888d389301611a69821f1cf4aa7b27c7168d6f 100644 (file)
--- a/org.eclipse.linuxtools.lttng.help/doc/User-Guide.mediawiki
+++ b/org.eclipse.linuxtools.lttng.help/doc/User-Guide.mediawiki
@@ -170,7 +170,6 @@ In addition to these views, the '''Tracing and Monitoring Framework (TMF)''' fea
 * [[#Colors_View | Colors View]]
 * [[#Filters_View | Filters View]]
 * [[#Time_Chart_View  | Time Chart View]]
-* [[#Environment_Variables_View  | Environment Variables View]]
 * [[#State_System_Explorer_View | State System Explorer View]]
 * [[#Call_Stack_View | Call Stack View]]
 
@@ -669,11 +668,6 @@ When a filter is applied in the events table, the non-matching ticks are removed
 
 The Time Chart only supports traces that are opened in an editor. The use of an editor is specified in the plug-in extension for that trace type, or is enabled by default for custom traces.
 
-== Environment Variables View ==
-A new feature of CTF traces is their ability to store user defined data that is not to be placed in an event. It is generally data that is per-trace specific, such as the tracer version and the trace domain. It will be populated when a trace is loaded if the trace has environment variables. <br>
-[[Image:images/LTTng2EnvironmentsView.png]]<br>
-The above picture shows a trace loaded that was collected with the '''lttng-modules''' version '''2'''.'''0'''.'''0''' tracer. It is a '''kernel''' trace of the '''3.2.0-18-generic''' '''linux''' kernel.
-
 == State System Explorer View ==
 
 The State System Explorer view allows the user to inspect the state interval values of every attribute of a state system at a particular time.

diff --git a/org.eclipse.linuxtools.lttng.help/doc/images/tracePackageImages/importTraceFolder.png b/org.eclipse.linuxtools.lttng.help/doc/images/tracePackageImages/importTraceFolder.png
index 2bae4f55026f75a62ff27adaabebb86956184d8c..79281df77b4eeba4b5703d3346ef587743ced0e7 100644 (file)
Binary files a/org.eclipse.linuxtools.lttng.help/doc/images/tracePackageImages/importTraceFolder.png and b/org.eclipse.linuxtools.lttng.help/doc/images/tracePackageImages/importTraceFolder.png differ

diff --git a/org.eclipse.linuxtools.tmf.help/doc/Developer-Guide.mediawiki b/org.eclipse.linuxtools.tmf.help/doc/Developer-Guide.mediawiki
index 1d92f83bb088320c7ed28eeb52894701fb25693b..5639a1ca26466c219d37fbafa6dd5298a7576c5a 100644 (file)
--- a/org.eclipse.linuxtools.tmf.help/doc/Developer-Guide.mediawiki
+++ b/org.eclipse.linuxtools.tmf.help/doc/Developer-Guide.mediawiki
@@ -3463,7 +3463,7 @@ public class AnalysisBenchmark {
 
 For more information, see [http://wiki.eclipse.org/Performance/Automated_Tests The Eclipse Performance Test How-to]
 
-Some rules to help write performance tests are explained in section [[ABC of performance testing | ABC of performance testing]].
+Some rules to help write performance tests are explained in section [[#ABC of performance testing | ABC of performance testing]].
 
 === Run a performance test ===