From: Ian Campbell <Ian.Campbell@citrix.com>
To: "Marcos E. Matsunaga" <Marcos.Matsunaga@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: xen 4.5 build broke at eed8d774ce19dcae26e1cc077088397681ad65eb
Date: Thu, 15 Jan 2015 10:18:01 +0000 [thread overview]
Message-ID: <1421317081.19103.320.camel@citrix.com> (raw)
In-Reply-To: <54B71BA9.9020801@oracle.com>
On Wed, 2015-01-14 at 20:45 -0500, Marcos E. Matsunaga wrote:
> Hi Folks,
>
> We have a daily build process for xen 4.5 and while checking the last
> few days build, I found an error that was introduced by
>
> 1166ecf tools/Rules.mk: Don't optimize debug builds; add macro debugging
> information
I think you (or your tools) have missed the creation of the Xen 4.5
branch (staging-4.5 + stable-4.5). This change is only in the staging
branch which is now the target for 4.6 development.
The issue you reported has been reported by Wen Congyang who has posted
patches too, something should be committed shortly.
Ian
next prev parent reply other threads:[~2015-01-15 10:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 1:45 xen 4.5 build broke at eed8d774ce19dcae26e1cc077088397681ad65eb Marcos E. Matsunaga
2015-01-15 10:18 ` Ian Campbell [this message]
2015-01-15 14:07 ` Marcos E. Matsunaga
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=1421317081.19103.320.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Marcos.Matsunaga@oracle.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.