From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: pyro branch for meta-openembedded, meta-qt5 / maintainer wanted
Date: Wed, 26 Apr 2017 20:44:22 +0200 [thread overview]
Message-ID: <20170426184422.GG3258@jama> (raw)
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Hello,
as every 6 months I'm looking for some volunteer(s) to step-up and
maintain "pyro" release branch.
You can sign-up by replying to this thread and then one of you need to
send README update like this:
https://github.com/openembedded/meta-openembedded/commit/3082e30da58df0711182cf114c71a8c6a093aeae
More details in thread searching for daisy maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2014-April/095601.html
http://lists.openembedded.org/pipermail/openembedded-devel/2014-May/095694.html
or dizzy maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2014-October/098441.html
or fido maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2015-March/100901.html
or jethro maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2015-October/103810.html
or krogoth maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2016-April/106952.html
or morty maintainer:
http://lists.openembedded.org/pipermail/openembedded-devel/2016-October/109452.html
Regards,
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next reply other threads:[~2017-04-26 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 18:44 Martin Jansa [this message]
2017-04-26 20:24 ` pyro branch for meta-openembedded, meta-qt5 / maintainer wanted akuster808
2017-05-04 14:02 ` Martin Jansa
2017-05-05 22:52 ` akuster808
2017-05-06 6:35 ` Martin Jansa
2017-05-07 8:19 ` Trevor Woerner
2017-10-25 5:46 ` akuster808
2017-10-25 6:20 ` Martin Jansa
2017-10-25 6:25 ` Philip Balister
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=20170426184422.GG3258@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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.