From: Denys Dmytriyenko <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Morty maintainer
Date: Wed, 16 Nov 2016 23:08:50 -0500 [thread overview]
Message-ID: <20161117040850.GC26131@denix.org> (raw)
In-Reply-To: <1479296981.28508.18.camel@linuxfoundation.org>
On Wed, Nov 16, 2016 at 11:49:41AM +0000, Richard Purdie wrote:
> Armin has kindly volunteered to maintain the morty stable release
> branch and has already put together a great series.
>
> I don't want to overload Armin so if anyone else wants to step forward,
> let me know and we can discuss it. Right now its looking likely Armin
> will be the maintainer though (thanks Armin!).
I'd like to offer Armin my help with this task, as I'm not sure I'll be able
to completely replace him yet. Will that work?
--
Denys
next prev parent reply other threads:[~2016-11-17 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 11:49 Morty maintainer Richard Purdie
2016-11-17 4:08 ` Denys Dmytriyenko [this message]
2016-12-21 20:39 ` Denys Dmytriyenko
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=20161117040850.GC26131@denix.org \
--to=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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