From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] kernel-shark-qt: Add I/O for configuration data.
Date: Fri, 17 Aug 2018 11:34:51 -0400 [thread overview]
Message-ID: <20180817113451.52db13d1@gandalf.local.home> (raw)
In-Reply-To: <7949286d-dd20-3ec7-4d8f-4e8356432f84@gmail.com>
On Fri, 17 Aug 2018 18:29:49 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:
> > I was actually thinking of having a single json file that stores all
> > "full sessions". Like a .viminfo file.
>
> This is a good idea.
>
> But we have to support saving individual sessions as well. Mainly for
Makes sense.
-- Steve
> bug reports. In my work directory I have a lot of files called
> bugXX.json ;-)
>
> Actually we can add a menu for creating a tarball containing trace.dat
> and session.json.
>
next prev parent reply other threads:[~2018-08-17 18:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:07 [PATCH v3 1/3] kernel-shark-qt: Add Json-C as a third party dependency Yordan Karadzhov (VMware)
2018-08-16 15:07 ` [PATCH v3 2/3] kernel-shark-qt: Add I/O for configuration data Yordan Karadzhov (VMware)
2018-08-16 18:52 ` Steven Rostedt
2018-08-17 9:32 ` Yordan Karadzhov (VMware)
2018-08-17 12:49 ` Steven Rostedt
2018-08-17 14:13 ` Yordan Karadzhov (VMware)
2018-08-17 14:58 ` Steven Rostedt
2018-08-17 15:09 ` Yordan Karadzhov (VMware)
2018-08-17 15:12 ` Steven Rostedt
2018-08-17 15:29 ` Yordan Karadzhov (VMware)
2018-08-17 15:34 ` Steven Rostedt [this message]
2018-08-17 9:34 ` Yordan Karadzhov (VMware)
2018-08-17 12:52 ` Steven Rostedt
2018-08-17 14:15 ` Yordan Karadzhov (VMware)
2018-08-16 15:07 ` [PATCH v3 3/3] kernel-shark-qt: Add an example showing how to import/export config. data Yordan Karadzhov (VMware)
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=20180817113451.52db13d1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=y.karadz@gmail.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).