From: Eric Blake <eblake@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, samuel.thibault@ens-lyon.org,
jan.kiszka@siemens.com, berrange@redhat.com
Subject: Re: [Qemu-devel] [PATCH for 2.10] slirp/smb: Replace constant strings by glib string
Date: Fri, 7 Apr 2017 10:03:58 -0500 [thread overview]
Message-ID: <130e1495-72f5-7ab5-0f25-0e3cb65006dc@redhat.com> (raw)
In-Reply-To: <20170407145634.GA2623@work-vm>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On 04/07/2017 09:56 AM, Dr. David Alan Gilbert wrote:
>
>> The cleanup is useful, and resolves one of the build issues I pointed
>> out earlier on Rawhide (looks like it is now Fedora 26 in addition to
>> Rawhide that have new-enough gcc). In that thread, we argued that it's
>> not going to be essential to get this in for 2.9, but as more and more
>> people move to newer gcc, it will probably be a candidate for
>> qemu-stable for 2.9.1 in addition to 2.10.
>
> Ah which thread is that?
https://lists.gnu.org/archive/html/qemu-devel/2017-03/threads.html#04552
in particular
https://lists.gnu.org/archive/html/qemu-devel/2017-03/msg04567.html
> I just posted:
> https://lists.nongnu.org/archive/html/qemu-devel/2017-04/msg01294.html
Yes, I just saw that. And it is indeed hacky, but maybe it will spur
some proper patches.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-04-07 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:32 [Qemu-devel] [PATCH for 2.10] slirp/smb: Replace constant strings by glib string Dr. David Alan Gilbert (git)
2017-04-07 14:54 ` Eric Blake
2017-04-07 14:56 ` Dr. David Alan Gilbert
2017-04-07 15:03 ` Eric Blake [this message]
2017-04-07 15:14 ` Dr. David Alan Gilbert
2017-04-08 21:55 ` Samuel Thibault
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=130e1495-72f5-7ab5-0f25-0e3cb65006dc@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.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).