From: Saul Wold <sgw@linux.intel.com>
To: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Status of Patches & Pull Requests
Date: Tue, 02 Aug 2011 09:39:23 -0700 [thread overview]
Message-ID: <4E38283B.5070206@linux.intel.com> (raw)
Folks,
Thanks for your patience, I am working with Richard to gather up the
requests that have been made over the last week. Now that we are
getting Milestone 3 moving again, OE-Core will get the attention it needs.
I am working to get patches in on a 24-48 hour cycle, so please have
some patience. If you don't see your patch in after 2 CONSOLIDATED pull
cycles or a response email it means I missed it! This is not a hard and
fast rule, as we are in constant flux. We are working on improving this
process with possibly using patchworks or something similar for the 1.2
timeframe.
As we move to Milestone 4 for Yocto, things will change again, as
Richard has already pointed out we are looking for more stabilizing
changes than updates or rewrites. At some point in mid-late August we
will branch 1.1_M4 and then cherry pick changes from Master.
--
Sau!
Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System
reply other threads:[~2011-08-02 16:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E38283B.5070206@linux.intel.com \
--to=sgw@linux.intel.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