From: michel.dagenais@polymtl.ca (Michel Dagenais)
Subject: [ltt-dev] RFC LTTv TextDump
Date: Wed, 24 Nov 2010 14:11:46 -0500 [thread overview]
Message-ID: <4CED6372.7050203@polymtl.ca> (raw)
In-Reply-To: <4CEC182E.5020805@polymtl.ca>
>> Note that the textdump can output content coming from multiple traces,
>> where having the trace name in the output for each event becomes
>> convenient.
The problem is having the full path, a short "id" when interleaved
events are there would be useful (something about hostname and CPU)
myhost p1
yourhost p1
myhost p1
myhost p2
next prev parent reply other threads:[~2010-11-24 19:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 20:20 David Goulet
2010-11-22 20:52 ` Alexandre Montplaisir
2010-11-23 18:26 ` Mathieu Desnoyers
2010-11-23 19:38 ` Alexandre Montplaisir
2010-11-23 20:15 ` Mathieu Desnoyers
2010-11-24 19:11 ` Michel Dagenais [this message]
2010-11-24 20:43 ` David Goulet
2010-11-24 22:49 ` Julien Desfossez
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=4CED6372.7050203@polymtl.ca \
--to=michel.dagenais@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