From: Henning Heinold <henning@itconsulting-heinold.de>
To: "Maxin B. John" <maxin.john@intel.com>
Cc: Mark Asselstine <mark.asselstine@windriver.com>,
Otavio Salvador <otavio.salvador@ossystems.com.br>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-java] maintainer status
Date: Mon, 11 Jun 2018 14:08:47 +0200 [thread overview]
Message-ID: <20180611120847.GB16619@mail.itconsulting-heinold.de> (raw)
In-Reply-To: <20180611113035.GA17777@mbabyjoh-desk.ger.corp.intel.com>
On Mon, Jun 11, 2018 at 02:30:35PM +0300, Maxin B. John wrote:
> Hi Richard,
>
> Sorry for my long silence here in the list ( was away due to a personal loss).
>
>
> On Thu, Jun 07, 2018 at 04:32:36PM +0200, prvs=68935beb6=Richard.Leitner@skidata.com wrote:
> > On 06/07/2018 03:56 PM, Otavio Salvador wrote:
> > > On Thu, Jun 7, 2018 at 10:53 AM, Richard Leitner
> > > <richard.leitner@skidata.com> wrote:
> > > ....
> > >> As I'm using this layer now for quite a few years I'll be glad to help you with
> > >> the maintainership of meta-java. Nonetheless I have to admit that I have no
> > >> experience in maintaining an openembedded layer ;-)
> > >> Therefore if you're still interested I'd have some questions regarding the
> > >> "strategic" targets, workflows and stuff like that...
> > >
> > > Awesome, new energy!
>
> Great !
>
> > > Sure, go ahead and ask :-D
> > >
> >
> > Thanks :-)
> >
> > So here are some question that currently came to my mind:
> >
> > * do you use some kind of patch management software (like patchwork)?
>
> meta-java doesn't use patchwork till now.
Yes, but we are using the normal the oe mailinglist, that is why you can find
the patches with the meta-java tag in the current patchwork too.
Bye Henning
next prev parent reply other threads:[~2018-06-11 12:09 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
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 [this message]
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=20180611120847.GB16619@mail.itconsulting-heinold.de \
--to=henning@itconsulting-heinold.de \
--cc=mark.asselstine@windriver.com \
--cc=maxin.john@intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio.salvador@ossystems.com.br \
--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 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.