From: Philip Tricca <flihp@twobit.us>
To: "T.O. Radzy Radzykewycz" <radzy@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-selinux][PATCH] swig is in meta-oe, remove this copy
Date: Sat, 27 Feb 2016 18:09:14 -0800 [thread overview]
Message-ID: <56D256CA.2040009@twobit.us> (raw)
In-Reply-To: <33006C99F5A5194A9B7A7715DFA3E383EB81CE0C@ALA-MBB.corp.ad.wrs.com>
On 02/24/2016 09:53 AM, Radzykewycz, T (Radzy) wrote:
>
> ________________________________________
>> From: Burton, Ross [ross.burton@intel.com]
>> Sent: Wednesday, February 24, 2016 9:10 AM
>> To: Radzykewycz, T (Radzy)
>> Cc: Hatle, Mark; yocto@yoctoproject.org
>> Subject: Re: [yocto] [meta-selinux][PATCH] swig is in meta-oe, remove this copy
>>
>> On 22 February 2016 at 14:51, Radzykewycz, T (Radzy) <radzy@windriver.com<mailto:radzy@windriver.com>> wrote:
>> It's easy enough to update the one in meta-selinux, if the decision is
>> to keep the duplicate. I have a 3.0.6 => 3.0.8 update ready to upload
>> to meta-oe, and I can do meta-selinux at the same time.
>>
>> In master at least, swig isn't in meta-oe and oe-core has 3.0.8 already. oe-core jethro has 3.0.6. Basically, there's no reason for anything targeting jethro onwards to ship swig.
>>
>> Ross
>
> Thanks, Ross.
>
> Yes, I realized yesterday that I had been working on an older branch. So
> no change is needed.
Thanks Radzy. I'm just catching up on this thread. It looks like swig
was removed from meta-selinux in
321848ab57d7d68c2033d22af1bedd3b86cafc3b so I'm leaving this alone.
Thanks,
Philip
next prev parent reply other threads:[~2016-02-28 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 22:59 [meta-selinux][PATCH] swig is in meta-oe, remove this copy T.O. Radzy Radzykewycz
2016-02-22 14:40 ` Mark Hatle
2016-02-22 14:51 ` Radzykewycz, T (Radzy)
2016-02-24 17:10 ` Burton, Ross
2016-02-24 17:53 ` Radzykewycz, T (Radzy)
2016-02-28 2:09 ` Philip Tricca [this message]
2016-02-22 15:33 ` Joe MacDonald
2016-02-22 15:57 ` Philip Balister
2016-02-22 15:58 ` Burton, Ross
2016-02-22 16:07 ` Joe MacDonald
2016-02-22 16:19 ` Martin Jansa
2016-02-22 17:55 ` Mark Hatle
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=56D256CA.2040009@twobit.us \
--to=flihp@twobit.us \
--cc=radzy@windriver.com \
--cc=yocto@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.