From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: 1.5/dora stable series maintainer
Date: Wed, 30 Oct 2013 13:45:54 +0000 [thread overview]
Message-ID: <1383140754.25877.27.camel@ted> (raw)
It gives me pleasure to announce that Robert Yang
<liezhi.yang@windriver.com> is going to be taking on the role of stable
maintainer for the 1.5 series.
The usual process for patch nomination and merging will happen with
Robert maintaining a dora-next branch which periodically will get merged
into the main dora branch after testing through a consolidated pull
request.
To "hit the ground running" so to speak, I fast forwarded dora a little
way along the master branch to take advantage of fixes which didn't
make the main release but were available when I started merging patches.
Further patches can be nominated and cherry-picked as needed from here.
Cheers,
Richard
reply other threads:[~2013-10-30 13:46 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=1383140754.25877.27.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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