<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hey tracing architects, <br>
Just a thought of consistency. <br>
we have <br>
lttng add-context (you can have many)<br>
lttng disable-context <br>
lttng enable-consumer (you can only have one)<br>
lttng disable-consumer <br>
I would suggest <br>
lttng add-trigger (you can have many)<br>
lttng disable-trigger<br>
lttng modify-trigger ??? <br>
<br>
<br>
TLDR: there should be a naming convention for lttng commands, there
probably are but I have not seen them, or maybe I have but I do not
remember seeing them. <br>
<br>
TLDR-TLDR: name things the same way please. :)<br>
<br>
<div class="moz-cite-prefix">On 13-04-11 12:08 PM, David Goulet
wrote:<br>
</div>
<blockquote cite="mid:5166DFE7.8020802@efficios.com" type="cite">
<pre wrap="">Hi everyone,
Here is the second RFC of the day.
By reading this, your imagination will probably go pretty crazy with
possibilities ;). The first implementation will only have one option
describe in the RFC but note that with this kind of feature, the sky is
the limit! and of course world domination is never far.
Thanks!
David
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
lttng-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:lttng-dev@lists.lttng.org">lttng-dev@lists.lttng.org</a>
<a class="moz-txt-link-freetext" href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>