From: Philippe Proulx via lttng-dev <lttng-dev@lists.lttng.org>
To: Aprameya Rao <Aprameya.Rao@microsoft.com>
Cc: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>,
lttng-dev <lttng-dev@lists.lttng.org>,
tracecompass-dev <tracecompass-dev@eclipse.org>,
Eric Warden <ericwarden@microsoft.com>
Subject: Re: [lttng-dev] CTF2-SPECRC-5.0
Date: Wed, 6 Apr 2022 20:56:53 -0400 (EDT) [thread overview]
Message-ID: <646071879.8391.1649293013412.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <SN6PR2101MB13433DE20434FDD6FECC80B681E69@SN6PR2101MB1343.namprd21.prod.outlook.com>
----- Original Message -----
> From: "Aprameya Rao" <Aprameya.Rao@microsoft.com>
> To: "Philippe Proulx" <pproulx@efficios.com>, "diamon-discuss" <diamon-discuss@lists.linuxfoundation.org>, "Eric Warden"
> <ericwarden@microsoft.com>
> Cc: "lttng-dev" <lttng-dev@lists.lttng.org>, "tracecompass-dev" <tracecompass-dev@eclipse.org>
> Sent: Wednesday, 6 April, 2022 20:51:33
> Subject: RE: CTF2-SPECRC-5.0
> Hi
>
> Is there a document that provides a diff between CTF1 and CTF2?
The CTF 2 specification proposal does; see
<https://diamon.org/ctf/files/CTF2-PROP-2.0rA.html#_changes_since_ctf1>.
There have been minor changes between CTF2-PROP-2.0 and CTF2-SPECRC-5.0;
see the "Revision history" section of CTF2-SPECRC-5.0 to learn more.
Philippe Proulx
EfficiOS Inc.
https://www.efficios.com/
>
> Thanks
> Aprameya
>
> -----Original Message-----
> From: lttng-dev <lttng-dev-bounces@lists.lttng.org> On Behalf Of Philippe Proulx
> via lttng-dev
> Sent: Wednesday, April 6, 2022 1:04 AM
> To: diamon-discuss <diamon-discuss@lists.linuxfoundation.org>
> Cc: lttng-dev <lttng-dev@lists.lttng.org>; tracecompass-dev
> <tracecompass-dev@eclipse.org>
> Subject: [EXTERNAL] [lttng-dev] CTF2-SPECRC-5.0
>
> Hello,
>
> This is an update of the CTF 2 specification release candidate from
> v4.0 to v5.0.
>
> This document, named CTF2-SPECRC-5.0, is available here:
>
> <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiamon.org%2Fctf%2Ffiles%2FCTF2-SPECRC-5.0.html&data=04%7C01%7Caprameya.rao%40microsoft.com%7C4bfcea22579c423d02be08da173b38b1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637847840395810150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=A%2Fyq3aTYQqYaqpfvlL9k17oLOuYm6OxWLMryIKFZnIQ%3D&reserved=0>
>
> See the first section, "Revision history", to learn what changed.
>
> As always, please feel free to provide feedback.
>
> Philippe Proulx
> EfficiOS Inc.
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fefficios.com%2F&data=04%7C01%7Caprameya.rao%40microsoft.com%7C4bfcea22579c423d02be08da173b38b1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637847840395810150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=AhDC1Ux4VudGgiah363vlBDTOmHyc9yJXLH1ccE6Bz8%3D&reserved=0
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.lttng.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Flttng-dev&data=04%7C01%7Caprameya.rao%40microsoft.com%7C4bfcea22579c423d02be08da173b38b1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637847840395810150%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ORy9ounXHajWfDfpa6dkokRZC0pkIVJ6s2r0TL4tYr8%3D&reserved=0
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2022-04-07 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 19:33 [lttng-dev] CTF2-SPECRC-5.0 Philippe Proulx via lttng-dev
2022-04-07 0:51 ` Aprameya Rao via lttng-dev
2022-04-07 0:56 ` Philippe Proulx via lttng-dev [this message]
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=646071879.8391.1649293013412.JavaMail.zimbra@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=Aprameya.Rao@microsoft.com \
--cc=diamon-discuss@lists.linuxfoundation.org \
--cc=ericwarden@microsoft.com \
--cc=pproulx@efficios.com \
--cc=tracecompass-dev@eclipse.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).