From: Ian Jackson <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xenproject.org
Cc: Ian Campbell <ian.campbell@citrix.com>
Subject: [OSSTEST PATCH 0/4] Miscellaneous bald yaks
Date: Tue, 29 Sep 2015 17:21:24 +0100 [thread overview]
Message-ID: <1443543688-1195-1-git-send-email-ian.jackson@eu.citrix.com> (raw)
There are two patches here to fix annoyances which can make
osstest-installed Debian guests hard to get into.
And two patches to reorganise slightly the runvar handling:
introducing a function `target_var' to replace `guest_var'. Currently
there is no real motivation for this except that it seems tidier.
(I thought I wanted this because I thought I wanted
TestSupport::await_tcp to know whether what it was probing was a
Debian install and if so what suite. I also have an unfinished patch
to set the target var specifying the suite, in all the places where we
do a Debian install. But I don't now think anything needs this so I
don't intend to finish that patch.)
I have done only fairly limited testing of the latter two patches. If
they seem like a thing we want to keep I will test them properly, at
least to discover if they seem to break anything.
Thanks,
Ian.
next reply other threads:[~2015-09-29 16:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:21 Ian Jackson [this message]
2015-09-29 16:21 ` [OSSTEST PATCH 1/4] ts-debian-fixup: Set password Ian Jackson
2015-09-29 16:21 ` [OSSTEST PATCH 2/4] Do not multiply console hvc0 getty entries Ian Jackson
2015-09-29 16:21 ` [OSSTEST PATCH 3/4] Runvar functions: Provide target_xenkernel_ver Ian Jackson
2015-09-29 16:21 ` [OSSTEST PATCH 4/4] Runvar functions: Introduce target_var and target_store_runvar Ian Jackson
2015-09-30 8:20 ` [OSSTEST PATCH 0/4] Miscellaneous bald yaks Ian Campbell
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=1443543688-1195-1-git-send-email-ian.jackson@eu.citrix.com \
--to=ian.jackson@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=xen-devel@lists.xenproject.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 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).