From: Kevin Wolf <kwolf@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] WIP: add GCoroutine support
Date: Thu, 15 Jan 2015 16:54:15 +0100 [thread overview]
Message-ID: <20150115155415.GE4361@noname.redhat.com> (raw)
In-Reply-To: <1420823990-31461-1-git-send-email-marcandre.lureau@gmail.com>
Am 09.01.2015 um 18:19 hat Marc-André Lureau geschrieben:
> Learn to use the GCoroutine library instead of qemu own coroutine
> implementation.
>
> GCoroutine is hosted on github:
> https://github.com/elmarco/gcoroutine
>
> This allows to share the same coroutine implementation between various
> projects (gtk-vnc and spice-gtk). It is related to the effort to push
> coroutine support in GLib. See also:
> https://bugzilla.gnome.org/show_bug.cgi?id=719362
Hm, I guess there might be uses for holding references after the
coroutine has exited if there are external references to the coroutine,
but is it useful not to drop one reference after the coroutine exits? I
guess in most cases, and in qemu always, the caller isn't aware that the
coroutine ended, so requiring an explicit call isn't as nice as it could
be.
Also, you modified the copyright lines. Would you mind restoring the
author names as in the original code, as their license requires? I see
that you also converted MIT licensed code into LGPL, without keeping the
original license text as required. For my code, I'm fine with the
conversion, but you should either have asked or left the original text
in place.
Kevin
next prev parent reply other threads:[~2015-01-15 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 17:19 [Qemu-devel] [PATCH] WIP: add GCoroutine support Marc-André Lureau
2015-01-09 17:32 ` Peter Maydell
2015-01-15 14:54 ` Stefan Hajnoczi
2015-01-15 15:08 ` Stefan Hajnoczi
2015-01-15 15:54 ` Kevin Wolf [this message]
2015-01-22 1:46 ` Marc-André Lureau
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=20150115155415.GE4361@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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).