Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][daisy] pull request, update README's, live555 fix
Date: Thu, 19 Jun 2014 13:57:01 +0200	[thread overview]
Message-ID: <20140619115701.GP2117@jama> (raw)
In-Reply-To: <CAOd_LFwu0hwLcU1+oAvK9TVtsbbawDhRqd=1wafXfOKOWw5T+g@mail.gmail.com>

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

On Thu, Jun 19, 2014 at 07:52:51AM -0400, Cliff Brake wrote:
> The following changes since commit dca466c074c9a35bc0133e7e0d65cca0731e2acf:
> 
>   python-efl: add dependency on python-dbus and lua to always build
> edje and elementary bindings (2014-05-12 10:08:28 +0200)
> 
> are available in the git repository at:
> 
>   https://github.com/cbrake/meta-openembedded.git daisy-to-merge
> 
> for you to fetch changes up to f3f1d14a6587d72388f50725b0a49c84cf417eb9:
> 
>   live555: fix fetch problem (2014-06-18 13:42:35 -0400)

Thank you!

Acked-By: Martin Jansa <Martin.Jansa@gmail.com>

Waiting for ACK from listed maintainers, then I'll merge it.

> ----------------------------------------------------------------
> Cliff Brake (1):
>       update maintainer info in README's for daisy
> 
> Steffen Sledz (1):
>       live555: fix fetch problem
> 
>  meta-efl/README                                | 16 ++++++++++++----
>  meta-filesystems/README                        | 15 +++++++++++----
>  meta-gnome/README                              | 16 ++++++++++++----
>  meta-gpe/README                                | 16 ++++++++++++----
>  meta-initramfs/README                          | 12 +++++++++---
>  meta-multimedia/README                         | 15 +++++++++++----
>  meta-networking/MAINTAINERS                    | 11 +++++++++--
>  meta-networking/README                         |  2 +-
>  meta-oe/README                                 | 14 +++++++++++---
>  meta-oe/recipes-multimedia/live555/live555.inc |  4 ++--
>  meta-perl/README                               | 13 ++++++++++---
>  meta-ruby/README                               | 17 +++++++++++++----
>  meta-systemd/README                            | 16 ++++++++++++----
>  meta-webserver/README                          | 13 ++++++++++---
>  meta-xfce/README                               | 16 ++++++++++++----
>  toolchain-layer/README                         | 14 +++++++++++---
>  16 files changed, 158 insertions(+), 52 deletions(-)
> -- 
> _______________________________________________
> 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 --]

  reply	other threads:[~2014-06-19 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 11:52 [meta-oe][daisy] pull request, update README's, live555 fix Cliff Brake
2014-06-19 11:57 ` Martin Jansa [this message]
2014-06-19 23:54   ` akuster808
2014-06-23 10:59   ` Martin Jansa
2014-06-23 13:21   ` Otavio Salvador
2014-06-20 16:04 ` Martin Jansa
2014-06-23 20:33   ` Cliff Brake
2014-06-24  0:02     ` Martin Jansa

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=20140619115701.GP2117@jama \
    --to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox