From: "Dongdong Zhang" <zhangdongdong@eswincomputing.com>
To: "John Snow" <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org, crosa@redhat.com, bleal@redhat.com
Subject: Re: Re: [PING PATCH 0/1] Fix some typos
Date: Fri, 6 Jan 2023 09:50:44 +0800 (GMT+08:00) [thread overview]
Message-ID: <2a334c7d.1060e.18584c5f906.Coremail.zhangdongdong@eswincomputing.com> (raw)
In-Reply-To: <CAFn=p-bnm5WgBO-eXTyuV+mPiCYaLM-rFaUVXY+kmU39GvwpZw@mail.gmail.com>
Hi John,
Could you help me relay these fixes?
If I submit a pull request, I will go through company's internal review process again.
Thanks a lot!
Dongdong
> -----原始邮件-----发件人:"John Snow" <jsnow@redhat.com>发送时间:2023-01-06 07:25:43 (星期五)收件人:"Dongdong Zhang" <zhangdongdong@eswincomputing.com>抄送:qemu-devel@nongnu.org, crosa@redhat.com, bleal@redhat.com主题:Re: [PING PATCH 0/1] Fix some typos
>
> On Thu, Dec 15, 2022 at 10:22 PM Dongdong Zhang
> <zhangdongdong@eswincomputing.com> wrote:
> >
> > Hi all,
> >
> > I would like to ping a patch
> >
> > https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg04568.html
> > https://lists.nongnu.org/archive/html/qemu-devel/2022-11/msg04570.html
> >
> >
> > > -----Original Messages-----From:"Dongdong Zhang" <zhangdongdong@eswincomputing.com>Sent Time:2022-11-30 09:53:57 (Wednesday)To:qemu-devel@nongnu.orgCc:jsnow@redhat.com, crosa@redhat.com, bleal@redhat.com, "Dongdong Zhang" <zhangdongdong@eswincomputing.com>Subject:[PATCH 0/1] Fix some typos
> > >
> > > This patch mainly fixes some typos in the 'python' directory.
> > >
> > > Dongdong Zhang (1):
> > > Fix some typos
> > >
> > > python/qemu/machine/console_socket.py | 2 +-
> > > python/qemu/machine/qtest.py | 2 +-
> > > python/qemu/qmp/protocol.py | 2 +-
> > > python/qemu/qmp/qmp_tui.py | 6 +++---
> > > 4 files changed, 6 insertions(+), 6 deletions(-)
> > >
> > > --
> > > 2.17.1
>
> ACK to this patch.
>
> For fixes under python/qemu/qmp/, I need to relay these fixes over to
> https://gitlab.com/qemu-project/python-qemu-qmp -- you can do it
> yourself and send a small merge request, or I can do it for you, if
> you'd like. Please let me know what you'd prefer, and then I will
> stage this patch.
>
> (Apologies that the code is duplicated in two repositories right
> now.... I'm working on fixing that.)
>
> --js
next prev parent reply other threads:[~2023-01-06 1:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 1:53 [PATCH 0/1] Fix some typos Dongdong Zhang
2022-11-30 1:53 ` [PATCH 1/1] " Dongdong Zhang
2022-11-30 8:29 ` Philippe Mathieu-Daudé
2023-01-16 18:10 ` Laurent Vivier
2023-01-16 20:06 ` John Snow
2023-01-05 23:57 ` Max Filippov
2022-12-16 3:22 ` [PING PATCH 0/1] " Dongdong Zhang
2023-01-05 23:25 ` John Snow
2023-01-06 1:50 ` Dongdong Zhang [this message]
2023-01-06 18:44 ` John Snow
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=2a334c7d.1060e.18584c5f906.Coremail.zhangdongdong@eswincomputing.com \
--to=zhangdongdong@eswincomputing.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).