From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH 0/2] ui: fix VNC endian regression & improve tracing
Date: Mon, 14 Jul 2025 09:22:22 +0100 [thread overview]
Message-ID: <aHS-Pm54ZIZTDpbd@redhat.com> (raw)
In-Reply-To: <887fbbd8-9e92-45b1-bdac-77d18a9b82bb@tls.msk.ru>
On Sat, Jul 12, 2025 at 11:26:29AM +0300, Michael Tokarev wrote:
> On 04.06.2025 19:22, Daniel P. Berrangé wrote:
> >
> > Daniel P. Berrangé (2):
> > ui: fix setting client_endian field defaults
> > ui: add trace events for all client messages
> >
> > ui/trace-events | 14 +++++++++++++
> > ui/vnc.c | 53 +++++++++++++++++++++++++++++++++++++++++++++++++
> > 2 files changed, 67 insertions(+)
>
> Hi!
>
> Has this series been forgotten? It seems it should be in 10.1
> and in 10.0.3. It has 2 R-Bs. Is it time to send a PullReq?
I have it pending a PR
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-07-14 8:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 16:22 [PATCH 0/2] ui: fix VNC endian regression & improve tracing Daniel P. Berrangé
2025-06-04 16:22 ` [PATCH 1/2] ui: fix setting client_endian field defaults Daniel P. Berrangé
2025-06-04 16:22 ` [PATCH 2/2] ui: add trace events for all client messages Daniel P. Berrangé
2025-06-04 18:32 ` [PATCH 0/2] ui: fix VNC endian regression & improve tracing Marc-André Lureau
2025-06-05 5:05 ` Philippe Mathieu-Daudé
2025-07-12 8:26 ` Michael Tokarev
2025-07-14 8:22 ` Daniel P. Berrangé [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=aHS-Pm54ZIZTDpbd@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).