From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Konstantin Kostiuk" <kkostiuk@redhat.com>,
qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Michael Roth" <michael.roth@amd.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH 0/2] build improvments
Date: Tue, 3 May 2022 09:59:14 +0100 [thread overview]
Message-ID: <YnDu4lkn9UPcspqX@redhat.com> (raw)
In-Reply-To: <0b0afdba-2f8f-1035-458b-f13d1f09f355@redhat.com>
On Fri, Apr 29, 2022 at 12:10:34AM +0200, Paolo Bonzini wrote:
> On 4/28/22 20:21, Konstantin Kostiuk wrote:
> > Konstantin Kostiuk (2):
> > configure: Add cross prefix for widl tool
> > qga-vss: always build qga-vss.tlb when qga-vss.dll is built
> >
> > configure | 3 +++
> > qga/vss-win32/meson.build | 4 ++--
> > 2 files changed, 5 insertions(+), 2 deletions(-)
>
> Both titles make sense, but they didn't reach the mailing list.
They did, but were each sent as standalone mail threads before this
cover letter was sent.
Konstantin: I'd suggest using 'git-publish' for sending patches in
future, as it automatically does the right thing, ensuring that the
threading is set correctly, and has many other benefits over sending
patch emails manually
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 :|
next prev parent reply other threads:[~2022-05-03 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 18:21 [PATCH 0/2] build improvments Konstantin Kostiuk
2022-04-28 22:10 ` Paolo Bonzini
2022-05-03 8:59 ` Daniel P. Berrangé [this message]
2022-05-03 9:41 ` Konstantin Kostiuk
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=YnDu4lkn9UPcspqX@redhat.com \
--to=berrange@redhat.com \
--cc=kkostiuk@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).