From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56563) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbXF0-0003qz-5N for qemu-devel@nongnu.org; Mon, 14 Sep 2015 13:08:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZbXEw-0004s5-3o for qemu-devel@nongnu.org; Mon, 14 Sep 2015 13:08:30 -0400 Received: from mx1.redhat.com ([209.132.183.28]:35264) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbXEv-0004rl-SW for qemu-devel@nongnu.org; Mon, 14 Sep 2015 13:08:26 -0400 References: <1441974836-17476-1-git-send-email-berrange@redhat.com> <87lhc9m1ys.fsf@blackfin.pond.sub.org> <3FBFD05D-A0A4-4A2C-A235-39923ECA7FAE@gmail.com> <55F6F8A0.50800@redhat.com> <21692175-E839-45FB-8DD1-FEC1E45BC37D@gmail.com> From: Eric Blake Message-ID: <55F6FF03.9000209@redhat.com> Date: Mon, 14 Sep 2015 11:08:19 -0600 MIME-Version: 1.0 In-Reply-To: <21692175-E839-45FB-8DD1-FEC1E45BC37D@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="QVLrPvwn6SlJbtv19eLVTtnqfB8HpIfIn" Subject: Re: [Qemu-devel] [PATCH v4] monitor: allow device_del to accept QOM paths List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Programmingkid Cc: Kevin Wolf , Jeff Cody , Markus Armbruster , qemu-devel@nongnu.org, Paolo Bonzini , =?UTF-8?Q?Andreas_F=c3=a4rber?= This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --QVLrPvwn6SlJbtv19eLVTtnqfB8HpIfIn Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 09/14/2015 10:49 AM, Programmingkid wrote: >> But you are worrying about nothing; although Kevin is waiting for a v3= , >> he has already mentioned on v2 that he is ready to queue auto-generati= on >> once it works: >> https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg00877.html >=20 > It has been a while since Kevin asked for a version 3. I wonder if the = author > of the patch knows about the version 3 request.=20 You're worrying about nothing (not to mention worrying on the wrong thread). The Red Hat engineers (including Jeff [as author of the thread you are worrying about], Kevin [as the maintainer that plans to take that patch], Paolo, Markus, myself [each listed on cc on this thread], and several others on the list) are fairly good about communicating with one another whenever a piece of work is blocking on someone else's actions, even if some of that communication occurs on private IRC channels instead of the list (to cut down on list traffic that is not as interesting to others). And from personal experience, frequent contributors on this list can be trusted to revise their patches as requested, without having to be prodded. And Red Hat has no monopoly on frequent contributors; Andreas [who is also on cc for this thread] is yet another example, out of many, of someone that will follow through with addressing review comments. Remember, just because patches don't land in 24 hours doesn't mean they aren't happening. Also, engineers may have multiple things on their plate, so while they will eventually get to responding to review comments, they may have other higher-priority tasks to attend to first. The 2.5 release freeze is still several weeks off, and it doesn't matter whether a patch lands today or in two weeks, if it is aiming to make it into the 2.5 release. Please exercise some patience. And while pings are sometimes appropriate, it is also reasonable to wait a least a week from the last activity on a thread, and then to ping on the thread you are worried about, rather than to side-track an unrelated thread where you may not even be reaching the right people. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --QVLrPvwn6SlJbtv19eLVTtnqfB8HpIfIn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJV9v8DAAoJEKeha0olJ0NqDXEIAJC4C7lff69qWGRltU0qRl0h Ss//Cjcbvq7cYqedK59khcGIWK3NlRMHgaFMc+rDEDFioZ2lLOeCn9NJzc3DsMwu z84mpJGkmLipmNCBitTUmZl52vdegceJYKZ5UbcjjETJ4s/d5B/deHeQWWWn699v Uy8jDAiAkbiujl+fu1L2J9mazKOUF3w7mx1hU/1k3EQ1PKavMRMsPHRcmimCBFxg m5LRIT7FjXbyC0wKWcYDHAhy0PbPGCbLYVPl/w7VWARzNevzKar7Qkz3TdyCaQyJ KAqVwMmccN5qARLOXcIPgZgVyvcNg7is0W/6y4Rpq0ptKK2YonqAYVmP4eCaLac= =F5jM -----END PGP SIGNATURE----- --QVLrPvwn6SlJbtv19eLVTtnqfB8HpIfIn--