From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Master branch merges
Date: Wed, 27 Jul 2011 15:30:37 -0700 [thread overview]
Message-ID: <4E30918D.2030304@linux.intel.com> (raw)
In-Reply-To: <1311758933.2344.342.camel@rex>
On 07/27/2011 02:28 AM, Richard Purdie wrote:
> We're coming up to an interesting point in the development cycle since a
> lot of the feature development work Yocto has been working on is winding
> up. It means there are a few significant patches waiting to go into
> master.
>
> Typically, life isn't straightforward and this is complicated by the
> fact I'll be in a black hole as far as modern communication goes for
> Thur/Fri/Sat.
>
> I've given what I should do under these circumstances a fair bit of
> thought and currently I'm thinking that the best approach is likely to
> merge everything that is ready. This is realistically the only way it
> will get the final round of testing.
>
> Its possible something will break. Fixes can easily be shared and queued
> up on a branch in my absence and Saul should be able to help with that
> if needed.
>
To help with this process, if there is patch for an M3 related problem,
please include M3 in the patch/pull request subject line so I can
quickly get to those this week.
Thanks
Sau!
> So this is a conscious decision and we'll see how it works out! :)
>
> Cheers,
>
> Richard
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2011-07-27 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 9:28 Master branch merges Richard Purdie
2011-07-27 22:30 ` Saul Wold [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=4E30918D.2030304@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 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.