Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: matthew.khouzam@ericsson.com (Matthew Khouzam)
Subject: [lttng-dev] TMF current and future developments
Date: Thu, 11 Oct 2012 13:19:08 -0400	[thread overview]
Message-ID: <5076FF8C.3040205@ericsson.com> (raw)
In-Reply-To: <5076FE7D.4050207@voxpopuli.im>

I would personally suggest checking out the state system. It is, in my
opinion, THE place to put abstracted events.
On 12-10-11 01:14 PM, Alexandre Montplaisir wrote:
> Hi Efraim,
>
> On 12-10-10 04:06 PM, Efraim Josue Lopez Sanchez wrote:
>> Hi,
>>
>> We are planning to build on top of TMF. Most recently we have tried
>> implementing some stuffs so that we can familiarize with TMF source
>> code. However, I've been wondering these last days about the future
>> plans/developments related to TMF. Is there any webpage/place/document
>> where I can find information regarding what are you guys
>> working/developing right now? And also about the future
>> developments/versions?
> If you want to track the very latest development, you can look at the
> patches that are going in for review on Gerrit, at
> https://git.eclipse.org/r/#/q/status:open+project:linuxtools/org.eclipse.linuxtools,n,z
> (not everything is related to TMF/LTTng, but it should be obvious what
> is by looking at the modified files).
>
> Most of it is targeted at the "lttng-kepler" branch on git, which should
> ultimately be part of the 2.0 release next June. If you want to try/test
> the latest code, you should use that branch.
>
> There is also a small list of planned features on
> http://eclipse.org/linuxtools/projectPages/lttng/ under "Future Plans".
>
> If you have any question about specific features, let us know!
>
>
> Cheers,
>




      reply	other threads:[~2012-10-11 17:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-10 20:06 Efraim Josue Lopez Sanchez
2012-10-11 17:14 ` Alexandre Montplaisir
2012-10-11 17:19   ` Matthew Khouzam [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=5076FF8C.3040205@ericsson.com \
    --to=matthew.khouzam@ericsson.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