From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Testing the kernels
Date: Wed, 25 Aug 2010 15:07:54 -0700 [thread overview]
Message-ID: <4C75943A.2000909@goop.org> (raw)
So as we discussed, we should split the testing of the toolstack and
the kernel into separate pieces so that kernel failures don't prevent
the toolstack tree from being updated.
I think you should use "xen/next-2.6.32" as the input to the test
subsystem. If you have a git tree on xenbits with a, say,
"xen/tested-2.6.32" branch which gets updated when the tests pass, then
I can make that automatically update xen/stable-2.6.32.x for public
consumption.
That way people who need/want bleeding edge changes can use
xen/next-2.6.32, and everyone else gets xen/stable-2.6.32.x by default.
J
next reply other threads:[~2010-08-25 22:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 22:07 Jeremy Fitzhardinge [this message]
2010-08-31 15:06 ` Testing the kernels Ian Jackson
2010-08-31 17:50 ` Jeremy Fitzhardinge
2010-08-31 17:54 ` Ian Jackson
2010-08-31 18:47 ` Pasi Kärkkäinen
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=4C75943A.2000909@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Jackson@eu.citrix.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 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).