From: Martin Jansa <martin.jansa@gmail.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: meta-perl, meta-filesystems maintenance
Date: Thu, 19 Sep 2013 14:55:15 +0200 [thread overview]
Message-ID: <20130919125515.GH18414@jama> (raw)
In-Reply-To: <20130913135936.GD11500@jama>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Fri, Sep 13, 2013 at 03:59:36PM +0200, Martin Jansa wrote:
> Hi,
>
> there were some patches for meta-perl, meta-filesystems
> do you want me to merge patches which looks OK without your ACK or
> should I always wait for it (you're listed in meta-perl as Maintainer
> and in meta-filesystems for couple of recipes + you created it)?
>
> If you don't have write access I'm OK with pushing them for you once
> they are acked on ML - or even better if you send me list of patchwork
> IDs to merge or some consolidated pull request.
>
> You can see what's in queue:
> http://patches.openembedded.org/bundle/jama/meta-filesystems/?archive=both
> http://patches.openembedded.org/bundle/jama/meta-perl/?archive=both
>
> If you don't have maintainer permission for patchwork, please ask Khem
> to add it for you.
ping
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-09-19 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 13:59 meta-perl, meta-filesystems maintenance Martin Jansa
2013-09-19 12:55 ` Martin Jansa [this message]
[not found] ` <1636291.7by8ZStO7f@helios>
[not found] ` <525616C1.4040905@windriver.com>
[not found] ` <20131014122216.GC3708@jama>
[not found] ` <525C993B.3040702@windriver.com>
[not found] ` <20131015112919.GA3703@jama>
[not found] ` <525E2D36.6050705@windriver.com>
2014-01-10 15:22 ` Martin Jansa
2014-01-10 15:33 ` Paul Eggleton
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=20130919125515.GH18414@jama \
--to=martin.jansa@gmail.com \
--cc=hongxu.jia@windriver.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.