From: Stefan Bader <stefan.bader@canonical.com>
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Subject: Xen 4.2 cherry-pick proposal
Date: Wed, 30 Jan 2013 10:12:57 +0100 [thread overview]
Message-ID: <5108E419.9060603@canonical.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 415 bytes --]
I could imagine that there will be other parties trying to compile Xen 4.2 on a
glibc >= 2.17 environment. So maybe this is worth being cherry-picked into the
stable-4.2 branch?
Cheers,
Stefan
From 5d98adc3e5e859ba23f62ca63450f6a60a9c5e2f Mon Sep 17 00:00:00 2001
From: Olaf Hering <olaf@aepfle.de>
Date: Thu, 6 Dec 2012 16:50:48 +0000
Subject: [PATCH] tools/gdbsx: fix build failure with glibc-2.17
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2013-01-30 9:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 9:12 Stefan Bader [this message]
2013-01-30 11:18 ` Xen 4.2 cherry-pick proposal Jan Beulich
2013-01-30 11:27 ` Stefan Bader
2013-01-30 15:17 ` Andrew Cooper
2013-02-15 15:07 ` Ian Jackson
2013-02-15 15:12 ` Jan Beulich
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=5108E419.9060603@canonical.com \
--to=stefan.bader@canonical.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xensource.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).