From: Tim Orling <timothy.t.orling@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-perl][PATCH] README: add self as maintainer
Date: Fri, 27 Oct 2017 07:42:47 -0700 [thread overview]
Message-ID: <20171027144247.17837-1-timothy.t.orling@linux.intel.com> (raw)
I have been, in practice, maintinaing meta-perl for several
years now. Given discussion at OEDEM, make it official.
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
---
meta-perl/README | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta-perl/README b/meta-perl/README
index 68160a628..67f291079 100644
--- a/meta-perl/README
+++ b/meta-perl/README
@@ -80,7 +80,9 @@ Send patches / pull requests to openembedded-devel@lists.openembedded.org with
When sending single patches, please using something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-perl][PATCH'
-Layer maintainer: Hongxu Jia <hongxu.jia@windriver.com>
+Layer maintainers:
+ Hongxu Jia <hongxu.jia@windriver.com>
+ Tim "moto-timo" Orling <ticotimo@gmail.com>
License
-------
--
2.13.5
reply other threads:[~2017-10-27 14:42 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=20171027144247.17837-1-timothy.t.orling@linux.intel.com \
--to=timothy.t.orling@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox