From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Jethro maintainer
Date: Tue, 24 Nov 2015 14:22:14 +0000 [thread overview]
Message-ID: <1448374934.31723.7.camel@linuxfoundation.org> (raw)
In-Reply-To: <1446816452.15270.171.camel@linuxfoundation.org>
On Fri, 2015-11-06 at 13:27 +0000, Richard Purdie wrote:
> We've going to need a new stable maintainer for the new release. There
> have already been a couple of offers, but to be fair to everyone I
> thought I'd explicitly ask if there was anyone else interested?
I've had discussions with a few people, thanks for the various offers.
I'm going to select Robert Yang as the stable maintainer for Jethro, not
least as the stable release he has been looking after is effectively out
of maintenance now.
Thanks Robert!
Cheers,
Richard
next prev parent reply other threads:[~2015-11-24 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 13:27 Jethro maintainer Richard Purdie
2015-11-20 16:45 ` Khem Raj
2015-11-24 14:22 ` Richard Purdie [this message]
2015-11-24 14:46 ` Robert Yang
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=1448374934.31723.7.camel@linuxfoundation.org \
--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