From: Doug Goldstein <cardoe@cardoe.com>
To: Derek Straka <derek@asterius.io>, meta-virtualization@yoctoproject.org
Subject: Re: [PATCH 2/4] xen: add the ability to configure the name of the policy
Date: Thu, 24 Mar 2016 12:55:27 -0500 [thread overview]
Message-ID: <56F42A0F.8000203@cardoe.com> (raw)
In-Reply-To: <1458833491-7717-2-git-send-email-derek@asterius.io>
[-- Attachment #1.1: Type: text/plain, Size: 351 bytes --]
On 3/24/16 10:31 AM, Derek Straka wrote:
> When using non-release versions, the policy files may have a different name (xenpolicy-${PV}-unstable). Allow the policy file name to be configured by the xen recipe.
>
> Signed-off-by: Derek Straka <derek@asterius.io>
> ---
Reviewed-by: Doug Goldstein <cardoe@cardoe.com>
--
Doug Goldstein
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 978 bytes --]
next prev parent reply other threads:[~2016-03-24 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 15:31 [PATCH 1/4] xen: split the flask package into a policy and tools package Derek Straka
2016-03-24 15:31 ` [PATCH 2/4] xen: add the ability to configure the name of the policy Derek Straka
2016-03-24 17:55 ` Doug Goldstein [this message]
2016-03-26 1:26 ` Chris Patterson
2016-03-28 13:06 ` Derek Straka
2016-03-28 14:23 ` Chris Patterson
2016-03-24 15:31 ` [PATCH 3/4] xen: add the flask policy to the set of files installed to the deploy directory Derek Straka
2016-03-24 17:55 ` Doug Goldstein
2016-03-24 15:31 ` [PATCH 4/4] xen: add the extra packages released with xen 4.7 Derek Straka
2016-03-24 17:56 ` Doug Goldstein
2016-03-24 17:55 ` [PATCH 1/4] xen: split the flask package into a policy and tools package Doug Goldstein
2016-03-25 17:59 ` Chris Patterson
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=56F42A0F.8000203@cardoe.com \
--to=cardoe@cardoe.com \
--cc=derek@asterius.io \
--cc=meta-virtualization@yoctoproject.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.