From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 219DFE009A7; Fri, 30 May 2014 07:17:16 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham version=3.3.1 X-Spam-HAM-Report: Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 66110E00724 for ; Fri, 30 May 2014 07:17:12 -0700 (PDT) Received: from [192.168.1.10] (c-68-38-40-177.hsd1.nj.comcast.net [68.38.40.177]) by smtp.webfaction.com (Postfix) with ESMTP id 75D6022859A4; Fri, 30 May 2014 14:17:11 +0000 (UTC) Message-ID: <538892E4.0@mindchasers.com> Date: Fri, 30 May 2014 10:17:08 -0400 From: Bob Cochran User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Lauren Post , "meta-freescale@yoctoproject.org" References: <9ce9a277dd774710ac5abbb649721d51@BLUPR03MB551.namprd03.prod.outlook.com> <5387FCD9.3010909@mindchasers.com> <878f27f5e5844ed3b4a6f9d02d01eb91@BLUPR03MB551.namprd03.prod.outlook.com> In-Reply-To: <878f27f5e5844ed3b4a6f9d02d01eb91@BLUPR03MB551.namprd03.prod.outlook.com> Subject: Re: Freescale Linux 3.10.31-1.1.0_alpha release is online X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2014 14:17:16 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 05/30/2014 09:53 AM, Lauren Post wrote: > >> For the repo manifest file (default.xml), can you use tag names (e.g., >> yocto-1.6) when possible instead of the SHA for your revision attribute inside of the project tag? It >> would save some time of having to do a reverse lookup for each revision attribute (commit) and make the > manifest more friendly. >> And how would I figure out why you chose a particular commit that wasn't otherwise notable / tagged >> (e.g., you're not using the 1.6 tag in meta-fsl-arm)? >> I looked through the commits in fsl-arm-yocto-bsp.git, but I didn't find anything to help me with this. > > When we do code freeze for a release we lock our manifest to specific commit on all layers - many times it is a mid point on the branches past the release. So unfortunately we can't use a tag or branch name in the manifest. After we release we go back to the tip and use that for development so our beta release will have more fixes from community from daisy branch. We always release based on latest official Yocto Project release so 3.10.31 is based off of daisy but will be upstreamed to be part of Yocto Project 1.7. Thanks for the reply Lauren. I see that you point to the poky revision that is indeed at the yocto-1.6 tag, but the meta-fsl-arm revision is not at the 1.6 tag. Other than combing through the mail lists, is there anything documented that would help me understand why you picked this particular commit for your release? (the answer is probably obvious to those that aren't playing catch up like me). > >> Lastly, I'm not able to clone fsl-arm-yocto-bsp.git. When I run: >> git clone git://git.freescale.com/imx/fsl-arm-yocto-bsp.git > > The manifest is only meant for repo init - not for git cloning. If you can, you might want to remove the git clone instructions at the bottom of the page: http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/?h=imx-3.10.31-1.1.0_alpha It is a just a basic repo so that we don't have to package our manifest in a release package as we did for earlier releases with i.MX with Yocto Project. > > Lauren Post > Freescale i.MX Yocto Project team lead > >