Hi Koen, On Thu, Jul 28, 2011 at 10:36 AM, Koen Kooi <k...@dominion.thruhere.net> wrote: > > Op 28 jul. 2011, om 16:29 heeft Ben Gardiner het volgende geschreven: > >> On Thu, Jul 28, 2011 at 10:24 AM, Frans Meulenbroeks >> <fransmeulenbro...@gmail.com> wrote: >>> >>> >>> 2011/7/28 Ben Gardiner <bengardi...@nanometrics.ca> >>>> >>>> >>>> Well, I would not submit _this_ patch for pull-request. I was hoping >>>> to get this version of raptor included and then submit a pull-request >>>> for a cherry-pick of the patch to add libxml2 to DEPENDS. >>> >>> Ah, missed that you also added libxml2. >>> Not sure about the policies of the maintenance branch, but I suspect the >>> proper way would be to fix and test in openembedded then submit a pull >>> request. >>> Then again maybe the policies for the maintenance branch are different. >> >> :) They are. AFAICT I need to get this recipe (including libxml2 dep >> update) into oe-core or its layers :) > > I ask again, what makes you think that? Pretty much all of the recent > maintenance commits are from .dev.
I'm sorry I guess my previous reply got lost in the noise. I think that because I read it from Tom. If it is at all possible to circumvent this requirement and avoid bothering you on the oe-core list that I would be happy to be obliged. On Thu, Jul 28, 2011 at 8:52 AM, Ben Gardiner <bengardi...@nanometrics.ca> wrote: > Hi Koen, Frans, > > On Thu, Jul 28, 2011 at 6:48 AM, Koen Kooi <k...@dominion.thruhere.net> wrote: >> [...] >> And where does it say it needs to be in OE-core first? > > My understanding of Tom's post to the oe.dev mailing list is that > commits in pull-requests for 2011.03 need to first be oe-core or one > of its layers. > > In Message-ID: <4dfa7108.5020...@mentor.com> On Thu, Jun 16, 2011 at > 5:09 PM, Tom Rini <tom_r...@mentor.com> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> As part of this weeks TSC meeting, an agenda item was brought up about >> the 2011.03-maintenance branch and oe-core / etc. I have now updated >> the policy about where changes need to be before they can be included in >> 2011.03-maintenance to include being in oe-core / meta-oe or other >> relevant public layer instead of being only in the oe.dev master branch. >> This is not a policy change, but a clarification of what was there >> previously. Thanks all! > As for getting it in meta-oe, you need to test it first in that layer before > sending a patch. Understood; I will test in meta-oe before sending a patch. Best Regards, Ben Gardiner --- Nanometrics Inc. http://www.nanometrics.ca _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
