From: Bob Cochran <yocto@mindchasers.com>
To: Lauren Post <Lauren.Post@freescale.com>,
"meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>
Subject: Re: Freescale Linux 3.10.31-1.1.0_alpha release is online
Date: Thu, 29 May 2014 23:36:57 -0400 [thread overview]
Message-ID: <5387FCD9.3010909@mindchasers.com> (raw)
In-Reply-To: <9ce9a277dd774710ac5abbb649721d51@BLUPR03MB551.namprd03.prod.outlook.com>
On 05/29/2014 03:25 PM, Lauren Post wrote:
> This is our release layer with readme describing how to download at
>
> http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/tree/README?h=imx-3.10.31-1.1.0_alpha
>
Hi Lauren,
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.
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
I get "warning: remote HEAD refers to nonexistent ref, unable to
checkout". Is this a bug? If so, where would I log it for this project?
Thank you,
Bob
next prev parent reply other threads:[~2014-05-30 3:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 19:25 Freescale Linux 3.10.31-1.1.0_alpha release is online Lauren Post
2014-05-29 22:48 ` Christian Betz
2014-05-29 23:27 ` Lauren Post
2014-05-30 0:15 ` Xh Xiao
2014-05-30 1:20 ` Otavio Salvador
2014-05-30 3:36 ` Bob Cochran [this message]
2014-05-30 13:53 ` Lauren Post
2014-05-30 14:17 ` Bob Cochran
2014-05-30 16:09 ` Otavio Salvador
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=5387FCD9.3010909@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=Lauren.Post@freescale.com \
--cc=meta-freescale@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.