From: Tom Zanussi <tom.zanussi@intel.com>
To: Jim Abernathy <jfabernathy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Build error while following Appendix A. Yocto Project Development manual
Date: Wed, 02 Nov 2011 10:34:33 -0500 [thread overview]
Message-ID: <1320248073.26655.86.camel@elmorro> (raw)
In-Reply-To: <1320246467.13661.10.camel@jim-ubuntu-10>
On Wed, 2011-11-02 at 08:07 -0700, Jim Abernathy wrote:
> > > Second, I looked at your cat of the same file containing the SRCREV
> > > commit strings and I don't see that they agree with the commits on the
> > > website even just this morning. Can you explain that? Should I just use
> > > the ones in your cat output or eventually the corrected Dev. Manual?
> > >
> >
> > I got these commits from the kernel .bb and .bbappends captured in the
> > edison branch, as mentioened above.
>
>
> That's a lot clearer now. So does this mean that If I'm working with
> edison branch, should I have to change the commits strings at all???
>
The commits in the doc should work - the SRCREV_machine is the last
commit on the edison branch for yocto/standard/common-pc/atom-pc and the
SRCREV_meta is also valid in edison, though in between the time the doc
was written and the time meta-intel was released for edison, the meta
SRCREV was bumped up to a later commit, which is the one I used in my
'cat'ed file. Either one should be fine. So no, you can directly use
the SRCREVS in the manual and don't have to change those at all.
> Because the commit strings from your cat'ing of the your file don't
> agree with what is in my clone of the edison branch for poky or
> meta-intel. Or am I missing something else (likely).
>
Those commit strings identify commits in the linux-yocto_3.0 repo
(http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-3.0/). The
specific commits used for edison are captured in the linux-yocto_3.0 .bb
and .bbappend files mentioned previously.
Tom
> Jim A
>
next prev parent reply other threads:[~2011-11-02 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 18:37 Build error while following Appendix A. Yocto Project Development manual James Abernathy
2011-11-01 19:40 ` Tom Zanussi
2011-11-01 19:48 ` James Abernathy
2011-11-01 19:55 ` Tom Zanussi
2011-11-01 20:04 ` James Abernathy
2011-11-02 0:45 ` Tom Zanussi
2011-11-02 12:19 ` Robert P. J. Day
2011-11-02 14:18 ` Tom Zanussi
2011-11-02 14:35 ` Robert P. J. Day
2011-11-02 14:24 ` Jim Abernathy
2011-11-02 14:41 ` Tom Zanussi
2011-11-02 15:07 ` Jim Abernathy
2011-11-02 15:34 ` Tom Zanussi [this message]
2011-11-02 19:18 ` Jim Abernathy
2011-11-02 19:36 ` Tom Zanussi
2011-11-02 20:07 ` Jim Abernathy
2011-11-02 20:18 ` Tom Zanussi
2011-11-02 22:05 ` Jim Abernathy
2011-11-03 19:32 ` James Abernathy
2011-11-01 21:37 ` Robert P. J. Day
2011-11-01 21:46 ` Tom Zanussi
2011-11-01 21:54 ` Tom Zanussi
2011-11-01 22:47 ` Robert P. J. Day
2011-11-01 23:16 ` Tom Zanussi
2011-11-01 23:27 ` Robert P. J. Day
2011-11-01 21:56 ` Robert P. J. Day
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=1320248073.26655.86.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=jfabernathy@gmail.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.