From: Mario Domenech Goulart <mario@parenteses.org>
To: Mark Asselstine <mark.asselstine@windriver.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-java] maintainer status
Date: Wed, 06 Jun 2018 09:38:25 +0200 [thread overview]
Message-ID: <87d0x4nz4e.fsf@parenteses.org> (raw)
In-Reply-To: <10630413.xVAl2E7OaH@yow-masselst-lx1> (Mark Asselstine's message of "Tue, 5 Jun 2018 11:11:26 -0400")
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
Hi Mark and all,
On Tue, 5 Jun 2018 11:11:26 -0400 Mark Asselstine <mark.asselstine@windriver.com> wrote:
> Several of us have noticed that nothing has been merged to meta-java since
> mid-April (roughly 8 weeks ago). With about a dozen commits sent to the list
> and pending merges I thought I might email you, the maintainers, directly to
> determine if this is expected to continue. Should we be looking to update the
> maintainers list and/or recruiting new people to restore the vitality of this
> repo? Have your roles or positions changed making it no longer viable for you
> to contribute to this repo?
>
> Thanks in advance for your responses.
I haven't been actively maintaining meta-java. Unfortunately I don't
have time to work on it anymore. Sorry about that.
Attached is a patch to remove myself from the list of maintainers.
All the best.
Mario
--
http://parenteses.org/mario
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-README-Remove-Mario-Goulart-from-the-list-of-maintai.patch --]
[-- Type: text/x-diff, Size: 764 bytes --]
From 00386a17fe0014bacec2bb98e534b7a81e698bd7 Mon Sep 17 00:00:00 2001
From: Mario Domenech Goulart <mario@parenteses.org>
Date: Wed, 6 Jun 2018 09:25:55 +0200
Subject: [meta-java][PATCH] README: Remove Mario Goulart from the list of
maintainers
Signed-off-by: Mario Domenech Goulart <mario@parenteses.org>
---
README | 1 -
1 file changed, 1 deletion(-)
diff --git a/README b/README
index 33511ff..1dfea95 100644
--- a/README
+++ b/README
@@ -45,7 +45,6 @@ When sending patches, please use something like:
Main layer maintainers:
Henning Heinold <henning@itconsulting-heinold.de>
- Mario Domenech Goulart <mario@ossystems.com.br>
Maxin John <maxin.john@intel.com>
Otavio Salvador <otavio@ossystems.com.br>
--
2.11.0
next prev parent reply other threads:[~2018-06-06 7:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 15:11 [meta-java] maintainer status Mark Asselstine
2018-06-05 15:18 ` Mark Asselstine
2018-06-05 15:51 ` Mark Asselstine
2018-06-05 16:48 ` Otavio Salvador
2018-06-05 17:45 ` Mark Asselstine
2018-06-06 7:38 ` Mario Domenech Goulart [this message]
2018-06-06 13:31 ` Mark Asselstine
2018-06-07 14:10 ` Mario Domenech Goulart
2018-06-07 14:14 ` Mark Asselstine
2018-06-06 20:42 ` Henning Heinold
2018-06-07 5:44 ` Richard Leitner
2018-06-07 13:22 ` Henning Heinold
2018-06-07 13:53 ` Richard Leitner
2018-06-07 13:56 ` Otavio Salvador
2018-06-07 14:11 ` Mark Asselstine
2018-06-07 14:32 ` Richard Leitner
2018-06-11 11:30 ` Maxin B. John
2018-06-11 12:08 ` Henning Heinold
2018-06-12 7:23 ` Richard Leitner
2018-06-12 20:59 ` Michael Halstead
2018-06-13 5:42 ` Richard Leitner
2018-06-13 10:05 ` Burton, Ross
2018-06-13 13:44 ` Richard Leitner
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=87d0x4nz4e.fsf@parenteses.org \
--to=mario@parenteses.org \
--cc=mark.asselstine@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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