From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Bader Subject: Xen 4.2 cherry-pick proposal Date: Wed, 30 Jan 2013 10:12:57 +0100 Message-ID: <5108E419.9060603@canonical.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1781678917301777197==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1781678917301777197== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig84AEBAA4A81AEB2BB66F062D" This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig84AEBAA4A81AEB2BB66F062D Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable I could imagine that there will be other parties trying to compile Xen 4.= 2 on a glibc >=3D 2.17 environment. So maybe this is worth being cherry-picked i= nto the stable-4.2 branch? Cheers, Stefan =46rom 5d98adc3e5e859ba23f62ca63450f6a60a9c5e2f Mon Sep 17 00:00:00 2001 From: Olaf Hering Date: Thu, 6 Dec 2012 16:50:48 +0000 Subject: [PATCH] tools/gdbsx: fix build failure with glibc-2.17 --------------enig84AEBAA4A81AEB2BB66F062D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBCgAGBQJRCOQhAAoJEOhnXe7L7s6j8oUP/R4DMVE55qZSLDCb/GAPTViK AOCFL0KPhR365hGgzvQEnefBtziystgLBpByf61XKHnx1VY2tbFv7WwVYhpJAJeo l7OI6lQNKOCD4FchitZI4YcTxDJFIB8GnAzUrlQ+omwWwO7prl2ygzZX7omCcXgJ vRHpwZwCxavtGaQx9wOb5Xi/QQZnCkQBo0ZJ51mAuGSeo0kJ9jQ2FVaAuTnDLIgF G1j/yeOTJaXCMuwQJJplvYzY8IvjszrkIvThakuX5b5douC2fQtTvYMqg1HAFc+t 6griwspt+s1UKLJZZnZFpkVywZAvPWkflBRO545BzGg4YPJctXUxBUDuPceLnA3O 2WVVPsppskq2h1840EY2IsA9hiGEggdBANfi6Wpa1I5bEZG3+utgJoL6X/2kw75g /8uzUy67F7gKI/EBMKgS5K4rJnZqg3igJ3K6xTEnriyLp+shUBH+uoZXgDniWExk 0K+28KsY+voPQOIH/OkyQiYNwd4Hzf9kvnkwWJTYfN9NVLHcebElkcsHmDGogu9X WOH9kZPPmbk8TUP/e+Q/1Wim87MC5mTUyCyS0ERgEkdq5i38xI8ygAkN37GfF1Tw zC9Z9USpO3c+e6I8RAjHFAFpJj2rJMgsfq6ht2Z2EBkPb6fiBc+O5BrfM+9fglMb 8AEXs4pWA3u3/OaAwi3D =qVnr -----END PGP SIGNATURE----- --------------enig84AEBAA4A81AEB2BB66F062D-- --===============1781678917301777197== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============1781678917301777197==--