All of lore.kernel.org
 help / color / mirror / Atom feed
From: akuster808 <akuster808@gmail.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>,
	 Armin Kuster <akuster@mvista.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>
Subject: Re: [PATCH 0/7] Remove use of PRINC
Date: Fri, 25 Jul 2014 19:43:08 -0000	[thread overview]
Message-ID: <53D2B338.906@gmail.com> (raw)
In-Reply-To: <CADkTA4OXMbtPKpfcDHQxRoDAGsGLzBrDJpZEMqV+q8NqOKoczg@mail.gmail.com>

Bruce,

Where there any objections?

- Armi

On 06/30/2014 09:39 PM, Bruce Ashfield wrote:
> On Mon, Jun 30, 2014 at 5:48 PM, Armin Kuster <akuster@mvista.com> wrote:
>> PR .= instead of PRINC
>>
>
> I have a similar series staged locally, but since I'm out of the
> office, I haven't
> pushed them yet.
>
> I staged these on top of that pending work, and if no one objects, I'll push
> everything at the same time.
>
> Bruce
>
>>
>> Armin Kuster (7):
>>    [meta-openstack] apache2: Remove PRINC reference
>>    [meta-openstack] iptables: remove PRINC reference
>>    [meta-openstack] lighttpd: remove PRINC reference
>>    [meta-openstack] postgressql: remove PRINC reference
>>    [meta-openstack] linux-yocto_3.10: remove PRINC reference
>>    [meta-openstack] linux-yocto_3.14: remove PRINC reference
>>    [meta-openstack] linux-yocto_3.4: remove PRINC reference
>>
>>   meta-openstack/recipes-extended/apache2/apache2_2.4.9.bbappend      | 2 +-
>>   meta-openstack/recipes-extended/iptables/iptables_1.4.21.bbappend   | 2 +-
>>   meta-openstack/recipes-extended/lighttpd/lighttpd_1.4.35.bbappend   | 2 +-
>>   meta-openstack/recipes-kernel/linux/linux-yocto_3.10.bbappend       | 3 ++-
>>   meta-openstack/recipes-kernel/linux/linux-yocto_3.14.bbappend       | 2 +-
>>   meta-openstack/recipes-kernel/linux/linux-yocto_3.4.bbappend        | 2 +-
>>   meta-openstack/recipes-support/postgresql/postgresql_9.2.4.bbappend | 2 +-
>>   7 files changed, 8 insertions(+), 7 deletions(-)
>>
>> --
>> 1.9.1
>>
>> --
>> _______________________________________________
>> meta-virtualization mailing list
>> meta-virtualization@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-virtualization
>
>
>


  parent reply	other threads:[~2014-07-25 19:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 21:48 [PATCH 0/7] Remove use of PRINC Armin Kuster
2014-06-30 21:48 ` [PATCH 1/7] [meta-openstack] apache2: Remove PRINC reference Armin Kuster
2014-06-30 21:48 ` [PATCH 2/7] [meta-openstack] iptables: remove " Armin Kuster
2014-06-30 21:48 ` [PATCH 3/7] [meta-openstack] lighttpd: " Armin Kuster
2014-06-30 21:48 ` [PATCH 4/7] [meta-openstack] postgressql: " Armin Kuster
2014-06-30 21:48 ` [PATCH 5/7] [meta-openstack] linux-yocto_3.10: " Armin Kuster
2014-06-30 21:48 ` [PATCH 6/7] [meta-openstack] linux-yocto_3.14: " Armin Kuster
2014-06-30 21:48 ` [PATCH 7/7] [meta-openstack] linux-yocto_3.4: " Armin Kuster
2014-07-01  4:39 ` [PATCH 0/7] Remove use of PRINC Bruce Ashfield
2014-07-01 21:14   ` akuster
2014-07-25 19:43   ` akuster808 [this message]
2014-07-27  2:43     ` Bruce Ashfield

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=53D2B338.906@gmail.com \
    --to=akuster808@gmail.com \
    --cc=akuster@mvista.com \
    --cc=bruce.ashfield@gmail.com \
    --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.