From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Seongab.Kim@harman.com
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open
Date: Thu, 23 Jul 2020 10:03:22 -0400 [thread overview]
Message-ID: <20200723140322.GA362716@joraj-alpa> (raw)
In-Reply-To: <CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.com>
> When your account gets activated, could you copy this into the new
> issue's description?
I manually activated it. You should be good to go.
>
> This way you can receive notifications when the issue gets updated.
>
> Thank you,
>
> Phil
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Rajotte-Julien via lttng-dev <lttng-dev@lists.lttng.org>
To: Seongab.Kim@harman.com
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] [EXTERNAL] Re: babeltrace cannot open the trace but Trace Compass can open
Date: Thu, 23 Jul 2020 10:03:22 -0400 [thread overview]
Message-ID: <20200723140322.GA362716@joraj-alpa> (raw)
Message-ID: <20200723140322.ANGwgCKr08WAMfO3ctD7Zm_3NttIW_mfgzG4hiqmLCk@z> (raw)
In-Reply-To: <CAB4xu_1p0AYHhb1GASzOM9e-pdWmSkeTfZq2tQoyacso1MCUNA@mail.gmail.com>
> When your account gets activated, could you copy this into the new
> issue's description?
I manually activated it. You should be good to go.
>
> This way you can receive notifications when the issue gets updated.
>
> Thank you,
>
> Phil
>
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2020-07-23 14:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 7:58 babeltrace cannot open the trace but Trace Compass can open Kim, Seongab via lttng-dev
2020-07-22 7:58 ` [lttng-dev] " Kim, Seongab via lttng-dev
2020-07-22 15:06 ` Philippe Proulx via lttng-dev
2020-07-22 15:06 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-07-23 9:08 ` [EXTERNAL] " Kim, Seongab via lttng-dev
2020-07-23 9:08 ` [lttng-dev] " Kim, Seongab via lttng-dev
2020-07-23 14:00 ` Philippe Proulx via lttng-dev
2020-07-23 14:00 ` [lttng-dev] " Philippe Proulx via lttng-dev
2020-07-23 14:03 ` Jonathan Rajotte-Julien via lttng-dev [this message]
2020-07-23 14:03 ` Jonathan Rajotte-Julien via lttng-dev
2020-07-23 14:10 ` Kim, Seongab via lttng-dev
2020-07-23 14:10 ` [lttng-dev] " Kim, Seongab via lttng-dev
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=20200723140322.GA362716@joraj-alpa \
--to=lttng-dev@lists.lttng.org \
--cc=Seongab.Kim@harman.com \
--cc=jonathan.rajotte-julien@efficios.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).