From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Zhao Liu <zhao1.liu@intel.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH] meson: Update meson-buildoptions.sh
Date: Mon, 15 Jul 2024 13:47:51 +0100 [thread overview]
Message-ID: <ZpUad0qRK2xBAnV5@redhat.com> (raw)
In-Reply-To: <ZpUdgyNb2lFga9PU@intel.com>
CC qemu-trivial
On Mon, Jul 15, 2024 at 09:00:51PM +0800, Zhao Liu wrote:
> Hi Daniel,
>
> On Fri, Jul 05, 2024 at 10:20:27AM +0100, Daniel P. Berrangé wrote:
> > Date: Fri, 5 Jul 2024 10:20:27 +0100
> > From: "Daniel P. Berrangé" <berrange@redhat.com>
> > Subject: Re: [PATCH] meson: Update meson-buildoptions.sh
> >
> > On Fri, Jul 05, 2024 at 01:49:03PM +0800, Zhao Liu wrote:
> > > Update meson-buildoptions.sh to stay in sync with meson_options.txt.
> > >
> > > Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> > > ---
> > > scripts/meson-buildoptions.sh | 14 +++++++-------
> > > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> >
>
> Thanks!
>
> BTW, could you please help merge this change? Because recently this
> script has been "polluting" my git staging workspace during
> development.
>
> Regards,
> Zhao
>
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:[~2024-07-15 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 5:49 [PATCH] meson: Update meson-buildoptions.sh Zhao Liu
2024-07-05 9:20 ` Daniel P. Berrangé
2024-07-15 13:00 ` Zhao Liu
2024-07-15 12:47 ` 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=ZpUad0qRK2xBAnV5@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
--cc=zhao1.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.