From: "MOESSBAUER, Felix via lttng-dev" <lttng-dev@lists.lttng.org>
To: "eeppeliteloop@gmail.com" <eeppeliteloop@gmail.com>
Cc: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: babeltrace | sink.ctf.fs: add support to create LTTng index
Date: Wed, 3 Dec 2025 09:58:22 +0000 [thread overview]
Message-ID: <3140f317060df66442077e0be78104695c873aca.camel@siemens.com> (raw)
In-Reply-To: <CAB4xu_0SBjk5xKXt_Q5gYWDC+iHg=oi08MyGyFhcBvvVmoAfvQ@mail.gmail.com>
On Mon, 2025-12-01 at 09:38 -0500, Philippe Proulx wrote:
> On Mon, Dec 1, 2025 at 4:34 AM MOESSBAUER, Felix via lttng-dev
> <lttng-dev@lists.lttng.org> wrote:
> >
> > Hi,
> >
> > I recently created a babeltrace pull request that adds support to
> > create an CTF LTTng index file along the CTF files [1].
> >
> > It would be great, if someone could review it.
>
> Thank you for your pull requests.
>
> I'll need to look at this in detail, but I'm not against the idea,
> especially if it's guarded behind a no-by-default
> initialization parameter.
That's how I implemented it.
>
> That being said:
>
> • We won't review on GitHub: please submit your change to our Gerrit
> Code Review system (<https://review.lttng.org/>).
>
> I know it's a bit more initial work on your side if you're not
> familiar with Gerrit, but the review process will be much easier.
>
> See <https://review.lttng.org/Documentation/user-upload.html> to learn
> how to upload a change.
It would be great to add this note to the contributing guide as well.
>
> For this reason, I'll close the PRs immediately.
>
> • You'll need to add a few tests to validate your feature.
Sure. I will add them as I now known that the feature in general is
well received within the babeltrace project
>
> • I'll deal with the documentation (manual pages) myself.
Thanks!
>
> • Given our current workload before the end of the year, I'm not sure
> I'll be able to review this before 2026.
No problem. For me it would be great, if you could briefly comment if
the chosen interface is OK (boolean input parameter called "create-
lttng-index"). By that, I can continue the integration in bt2-ftrace-
to-ctf [1] and once the feature becomes officially available I don't
need to change the plugin again.
[1] https://github.com/siemens/bt2-ftrace-to-ctf/pull/13
Best regards,
Felix
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
prev parent reply other threads:[~2025-12-03 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 9:34 MOESSBAUER, Felix via lttng-dev
2025-12-01 14:38 ` Philippe Proulx via lttng-dev
2025-12-03 9:58 ` MOESSBAUER, Felix via lttng-dev [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=3140f317060df66442077e0be78104695c873aca.camel@siemens.com \
--to=lttng-dev@lists.lttng.org \
--cc=eeppeliteloop@gmail.com \
--cc=felix.moessbauer@siemens.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