Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: otavio@ossystems.com.br
Subject: Re: [PATCH 00/15] Fido add maintainers
Date: Thu, 2 Apr 2015 04:04:28 +0200	[thread overview]
Message-ID: <20150402020428.GM14928@jama> (raw)
In-Reply-To: <cover.1427931203.git.akuster808@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]

On Wed, Apr 01, 2015 at 04:43:34PM -0700, Armin Kuster wrote:
> please consider these maintainers for the meta-openembdded fido branch
> 
> The following changes since commit df6c7b1279790d27ebfd58fbdfbac89bde5782ec:
> 
>   python-pyopenssl: Upgrade to 0.14 (2015-03-21 16:42:30 +0100)
> 
> are available in the git repository at:
> 
>   https://github.com/akuster/meta-openembedded akuster/fido-next
>   https://github.com//tree/akuster/fido-next

Would you mind (me) squashing them together so that it's easier to create the
patch for next release?

> Armin Kuster (15):
>   meta-efl: update maintainers list
>   meta-filesystems: update for fido maintainer
>   meta-gnome: update maintainers list
>   meta-gpe: update maintainers list
>   meta-initramfs: update maintainers list
>   meta-multimedia: update maintainers list
>   meta-networking: update maintainers list
>   meta-oe: update maintainers list
>   meta-perl: update maintainers list
>   meta-python: update maintainers list
>   meta-ruby: update maintainers list
>   meta-systemd: update maintainers list
>   meta-xfce: update maintainers list
>   meta-webserver: updated maintainers list
>   toolchain-layer: update maintainers list
> 
>  meta-efl/README             | 13 +++++++------
>  meta-filesystems/README     | 14 +++++++++-----
>  meta-gnome/README           | 12 +++++++-----
>  meta-gpe/README             | 13 +++++++------
>  meta-initramfs/README       | 11 ++++++-----
>  meta-multimedia/README      | 14 +++++++-------
>  meta-networking/MAINTAINERS |  8 ++++++--
>  meta-networking/README      |  6 +++---
>  meta-oe/README              | 11 ++++++-----
>  meta-perl/README            | 10 ++++++----
>  meta-python/README          | 11 +++++++----
>  meta-ruby/README            | 12 +++++++-----
>  meta-systemd/README         | 11 +++++++----
>  meta-webserver/README       | 13 ++++++++++---
>  meta-xfce/README            | 11 ++++++-----
>  toolchain-layer/README      |  9 ++++++---
>  16 files changed, 107 insertions(+), 72 deletions(-)
> 
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  parent reply	other threads:[~2015-04-02  2:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 23:43 [PATCH 00/15] Fido add maintainers Armin Kuster
2015-04-02  0:13 ` Otavio Salvador
2015-04-02  2:04 ` Martin Jansa [this message]
2015-04-02  4:36   ` akuster808

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=20150402020428.GM14928@jama \
    --to=martin.jansa@gmail.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