From: Yordan Karadzhov <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Jerome Marchand <jmarchan@redhat.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: Kernelshark: migrate to Qt 6
Date: Mon, 2 Oct 2023 21:43:28 +0300 [thread overview]
Message-ID: <d39af1f0-9e05-7c57-3248-4f5f16801e4b@gmail.com> (raw)
In-Reply-To: <20231002140136.6ae97dfc@gandalf.local.home>
On 10/2/23 21:01, Steven Rostedt wrote:
> On Mon, 2 Oct 2023 14:22:58 +0200
> Jerome Marchand <jmarchan@redhat.com> wrote:
>
>> Hi,
>>
>> Qt 5 is reaching end-of-life and Qt 5.15 appears to be the last Qt 5
>> version. Is there any plan to port kernelshark to Qt 6?
>>
>> I have no experience with Qt devel, but it seems that some effort has
>> been made to keep the migration easy:
>> https://doc.qt.io/qt-6/portingguide.html
>> https://www.qt.io/blog/porting-from-qt-5-to-qt-6-using-qt5compat-library
>>
>
> Thanks for notifying us.
Thanks a lot! I wasn't aware of this.
>
> Yordan, do you have any time to make the transition to Qt 6?
Yes, I will take care. It may take some time, but I geus it is not urgent.
cheers,
Y.
>
> -- Steve
>
prev parent reply other threads:[~2023-10-02 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 12:22 Kernelshark: migrate to Qt 6 Jerome Marchand
2023-10-02 18:01 ` Steven Rostedt
2023-10-02 18:43 ` Yordan Karadzhov [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=d39af1f0-9e05-7c57-3248-4f5f16801e4b@gmail.com \
--to=y.karadz@gmail.com \
--cc=jmarchan@redhat.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).