All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Leitner <richard.leitner@skidata.com>
To: OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-java] maintainer status
Date: Wed, 13 Jun 2018 07:42:14 +0200	[thread overview]
Message-ID: <32bd0cdd-2148-ff0b-feaa-64a4cbc21e38@skidata.com> (raw)
In-Reply-To: <CADfgfoY2fJOBt0ayVUfvyt1X079kDk=pc=7pswDmV=uPvuSA_A@mail.gmail.com>

Hi,

On 06/12/2018 10:59 PM, Michael Halstead wrote:
> 
> On Tue, Jun 12, 2018 at 12:23 AM, Richard Leitner
> <richard.leitner@skidata.com <mailto:richard.leitner@skidata.com>> wrote:
> 
>     Hi Maxin, Hi Henning,
> 
>     thank you for your answers!
> 
>     On 06/11/2018 02:08 PM, Henning Heinold wrote:
>     > On Mon, Jun 11, 2018 at 02:30:35PM +0300, Maxin B. John wrote:
>     >>>
>     >>> 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.
> 
>     Just saw it. Thanks for that hint.
>     So should we use it too?
>     IMHO it's a good tool for "not forgetting patches" ;-)
> 
>     AFAIK I still have an account there, but according to the login it's
>     "inactive".
>     May someone "re-activate" it please?
> 
> 
> I can help with patchwork. I'll e-mail you with a few questions.

Thank you Michael!

Another question just came to my mind:
How should I deal with my own patches?
Am I "allowed" to apply them myself or should another maintainer do
this? If I should do it on my own: How long should they "stay" on the
mailinglist before?

regards;Richard.L


  reply	other threads:[~2018-06-13  5:42 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
2018-06-12  7:23                 ` Richard Leitner
2018-06-12 20:59                   ` Michael Halstead
2018-06-13  5:42                     ` Richard Leitner [this message]
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=32bd0cdd-2148-ff0b-feaa-64a4cbc21e38@skidata.com \
    --to=richard.leitner@skidata.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 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.