From: michael.sills-lavoie@polymtl.ca (Michael Sills Lavoie)
Subject: [ltt-dev] Liblttd patch
Date: Tue, 16 Feb 2010 13:50:33 -0500 [thread overview]
Message-ID: <621276931002161050o7be8d81ag821f6aa4c14e4381@mail.gmail.com> (raw)
Message-ID: <20100216185033.P0QKoon79N7ffVQFeR7YSq6D4ZkLJkK-FGSxOQ01NDs@z> (raw)
Hey,
This is a working implementation of the new liblttd and lttd. This is only a
work in progress because we don't have the possibility to create multiple
instances of the "daemon" yet.
You can apply the patch with : git apply liblttd.patch in the ltt-control
root directory.
What do you think about it ?
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100216/defc76e7/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: liblttd.patch
Type: text/x-patch
Size: 54058 bytes
Desc: not available
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20100216/defc76e7/attachment-0002.bin>
next reply other threads:[~2010-02-16 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 18:50 Michael Sills Lavoie [this message]
2010-02-16 18:50 ` Michael Sills Lavoie
2010-02-16 19:35 ` Mathieu Desnoyers
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=621276931002161050o7be8d81ag821f6aa4c14e4381@mail.gmail.com \
--to=michael.sills-lavoie@polymtl.ca \
/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