X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fwhats-new.md;h=d5a00066ce982f091fb6888ad454ca9bbe84e69e;hb=85ccb28b9a18a29b9515e2d445185f8d0241c5f2;hp=9c4df4673b3cae60814d4bee375b7ca8066ea1f9;hpb=26418fc3d8c8cbc61fd73683a3e2e48bb19edb27;p=lttng-docs.git diff --git a/contents/whats-new.md b/contents/whats-new.md index 9c4df46..d5a0006 100644 --- a/contents/whats-new.md +++ b/contents/whats-new.md @@ -4,7 +4,7 @@ id: whats-new Most of the changes of LTTng 2.6 are bug fixes, making the toolchain more stable than ever before. Still, LTTng 2.6 adds some interesting -features. +features to the project. LTTng 2.5 already supported the instrumentation and tracing of [Java applications](#doc-java-application) through `java.util.logging` @@ -15,16 +15,16 @@ commands of the `lttng` tool. LTTng-modules has supported system call tracing for a long time, but until now, it was only possible to record either all of them, -or none of them. LTTng 2.6 allows the user to record only a specific -subset of system call events, e.g.: +or none of them. LTTng 2.6 allows the user to record specific +system call events, for example: 
 lttng enable-event --kernel --syscall open,fork,chdir,pipe
-Finally, the `lttng` command line tool cannot only communicate with -humans as it used to do, but also with machines thanks to its new +Finally, the `lttng` command line tool is not only able to communicate +with humans as it used to do, but also with machines thanks to its new [machine interface](#doc-mi) feature. To learn more about the new features of LTTng 2.6, see -[this release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/). +[the release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/).