From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Merging in latest yocto changes?
Date: Sat, 26 Feb 2011 10:47:47 -0700 [thread overview]
Message-ID: <4D693CC3.9080308@mentor.com> (raw)
In-Reply-To: <9E9CB5A5-E408-45DF-B2A1-DDD05DDFCF26@dominion.thruhere.net>
On 02/26/2011 01:26 AM, Koen Kooi wrote:
> Hi,
>
> Is anyone already working on merging in the latest yocto changes? I can take a stab at creating a patchset if noone is has already done that.
Since Khem is at SCALE and I'm watching over the release, I say go for it.
--
Tom Rini
Mentor Graphics Corporation
prev parent reply other threads:[~2011-02-26 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 8:26 Merging in latest yocto changes? Koen Kooi
2011-02-26 17:47 ` Tom Rini [this message]
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=4D693CC3.9080308@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox