From: Ian Campbell <ian.campbell@citrix.com>
To: "Xu, Quan" <quan.xu@intel.com>
Cc: Olaf Hering <olaf@aepfle.de>, Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: stubdom vtpm build failure in staging
Date: Thu, 12 Mar 2015 09:42:42 +0000 [thread overview]
Message-ID: <1426153362.21353.342.camel@citrix.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28890E8B382A@SHSMSX101.ccr.corp.intel.com>
On Thu, 2015-03-12 at 01:46 +0000, Xu, Quan wrote:
> I am still testing and fixing it. Sorry for that, I am not a full time
> open source developer.
Regardless, you are expect to fix things which you broke in a timely
manner, otherwise in the future I will just have to be more proactive
about reverting changes.
Certainly fixing things needs to take precedence over submissions of new
functionality.
Ian.
next prev parent reply other threads:[~2015-03-12 9:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 15:08 stubdom vtpm build failure in staging Olaf Hering
2015-01-28 15:13 ` Xu, Quan
2015-02-11 15:20 ` Olaf Hering
2015-02-12 16:56 ` Xu, Quan
2015-02-12 17:24 ` Xu, Quan
2015-02-12 17:40 ` Andrew Cooper
2015-02-13 2:07 ` Xu, Quan
2015-02-25 13:54 ` Ian Campbell
2015-02-27 15:07 ` Xu, Quan
2015-03-11 10:51 ` Ian Campbell
2015-03-12 1:46 ` Xu, Quan
2015-03-12 9:42 ` Ian Campbell [this message]
2015-03-12 15:44 ` Xu, Quan
2015-03-13 13:30 ` Olaf Hering
2015-03-13 15:39 ` Xu, Quan
2015-01-28 15:24 ` Ian Campbell
2015-01-29 7:34 ` Xu, Quan
2015-01-29 8:27 ` Olaf Hering
2015-01-29 9:22 ` Xu, Quan
2015-01-29 9:36 ` Olaf Hering
2015-01-29 10:27 ` Olaf Hering
2015-01-29 10:46 ` Ian Campbell
2015-01-30 8:09 ` Olaf Hering
2015-01-30 10:39 ` Ian Campbell
2015-01-30 11:03 ` 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=1426153362.21353.342.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=olaf@aepfle.de \
--cc=quan.xu@intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.