From: Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
To: gbastien+lttng@versatic.net, matthew.khouzam@ericsson.com,
diamon-discuss@linuxfoundation.org, pproulx@efficios.com,
jgalar@efficios.com
Cc: lttng-dev@lists.lttng.org
Subject: [RFC PATCH CTF 0/3] Common Trace Format Updates (upcoming 1.8.3)
Date: Thu, 23 Apr 2020 16:52:23 -0400 [thread overview]
Message-ID: <20200423205226.496-1-mathieu.desnoyers@efficios.com> (raw)
Hi,
We noticed a few unspecified areas in the CTF 1.8.2 specification which
require some clarifications. We therefore plan to do a 1.8.3 release of
the specification including those changes.
Review is welcome,
Thanks,
Mathieu
Geneviève Bastien (1):
Clarify that unlisted enum values are implementation-defined
Mathieu Desnoyers (2):
Clarify monotonicity requirement on timestamp begin
Clarify that timestamp begin/end need to be complete clock values
common-trace-format-specification.md | 20 +++++++++++++-------
1 file changed, 13 insertions(+), 7 deletions(-)
--
2.11.0
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next reply other threads:[~2020-04-23 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 20:52 Mathieu Desnoyers via lttng-dev [this message]
2020-04-23 20:52 ` [RFC PATCH CTF 1/3] Clarify that unlisted enum values are implementation-defined Mathieu Desnoyers via lttng-dev
2020-04-23 22:51 ` Jérémie Galarneau via lttng-dev
2020-04-24 14:05 ` Mathieu Desnoyers via lttng-dev
2020-04-24 14:05 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-04-28 18:40 ` Philippe Proulx via lttng-dev
2020-04-28 18:40 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-04-28 18:51 ` Mathieu Desnoyers via lttng-dev
2020-04-28 18:51 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-04-29 12:08 ` Mathieu Desnoyers via lttng-dev
2020-04-29 12:08 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-04-29 16:50 ` Philippe Proulx via lttng-dev
2020-04-29 16:50 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-04-23 20:52 ` [RFC PATCH CTF 2/3] Clarify monotonicity requirement on timestamp begin Mathieu Desnoyers via lttng-dev
2020-04-28 18:42 ` Philippe Proulx via lttng-dev
2020-04-28 18:42 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-04-28 18:54 ` Mathieu Desnoyers via lttng-dev
2020-04-28 18:54 ` [lttng-dev] " Mathieu Desnoyers via lttng-dev
2020-04-23 20:52 ` [RFC PATCH CTF 3/3] Clarify that timestamp begin/end need to be complete clock values Mathieu Desnoyers via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200423205226.496-1-mathieu.desnoyers@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=diamon-discuss@linuxfoundation.org \
--cc=gbastien+lttng@versatic.net \
--cc=jgalar@efficios.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=matthew.khouzam@ericsson.com \
--cc=pproulx@efficios.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).