From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga11.intel.com ([192.55.52.93]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QmCgn-0003Xt-HK for openembedded-core@lists.openembedded.org; Thu, 28 Jul 2011 00:34:53 +0200 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 27 Jul 2011 15:30:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,279,1309762800"; d="scan'208";a="35271480" Received: from unknown (HELO [10.255.14.61]) ([10.255.14.61]) by fmsmga001.fm.intel.com with ESMTP; 27 Jul 2011 15:30:37 -0700 Message-ID: <4E30918D.2030304@linux.intel.com> Date: Wed, 27 Jul 2011 15:30:37 -0700 From: Saul Wold User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc13 Thunderbird/3.1.10 MIME-Version: 1.0 To: Patches and discussions about the oe-core layer References: <1311758933.2344.342.camel@rex> In-Reply-To: <1311758933.2344.342.camel@rex> Subject: Re: Master branch merges X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jul 2011 22:34:53 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 07/27/2011 02:28 AM, Richard Purdie wrote: > We're coming up to an interesting point in the development cycle since a > lot of the feature development work Yocto has been working on is winding > up. It means there are a few significant patches waiting to go into > master. > > Typically, life isn't straightforward and this is complicated by the > fact I'll be in a black hole as far as modern communication goes for > Thur/Fri/Sat. > > I've given what I should do under these circumstances a fair bit of > thought and currently I'm thinking that the best approach is likely to > merge everything that is ready. This is realistically the only way it > will get the final round of testing. > > Its possible something will break. Fixes can easily be shared and queued > up on a branch in my absence and Saul should be able to help with that > if needed. > To help with this process, if there is patch for an M3 related problem, please include M3 in the patch/pull request subject line so I can quickly get to those this week. Thanks Sau! > So this is a conscious decision and we'll see how it works out! :) > > Cheers, > > Richard > > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >