From: akuster808 <akuster808@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Steffen Sledz <sledz@dresearch-fe.de>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][daisy][PATCH] live555: fix fetch problem
Date: Mon, 16 Jun 2014 09:36:37 -0700 [thread overview]
Message-ID: <539F1D15.8090304@gmail.com> (raw)
In-Reply-To: <20140616105942.GO2428@jama>
Martin,
You can add me as a meta-oe daisy maintainer, if there is still a need.
- Armin
On 06/16/2014 03:59 AM, Martin Jansa wrote:
> On Mon, Jun 16, 2014 at 11:45:12AM +0200, Steffen Sledz wrote:
>> On 16.06.2014 10:48, Paul Eggleton wrote:
>>> On Monday 16 June 2014 08:32:55 Steffen Sledz wrote:
>>>> What is the right ML address for patches in this area?
>>>>
>>>> The meta-multimedia/README in git://git.openembedded.org/meta-openembedded
>>>> (daisy branch) says:
>>>>
>>>> "Send pull requests to openembedded-devel@lists.openembedded.org"
>>>>
>>>> But i believe this should be openembedded-core@lists.openembedded.org.
>>>
>>> No, for all layers in the meta-openembedded repository it should be
>>> openembedded-devel as listed.
>>
>> OK, thx for this info.
>>
>> So i hope the patch will make it into the daisy branch in the next time, because our build is broken meanwhile (OK, we have a workaround, but this is unendearing).
>
> We still don't have meta-oe daisy maintainer :/ (and update to READMEs
> in daisy branch)..
>
>
>
next prev parent reply other threads:[~2014-06-16 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 19:44 [meta-oe][daisy][PATCH] live555: fix fetch problem Steffen Sledz
2014-06-16 6:32 ` Steffen Sledz
2014-06-16 8:48 ` Paul Eggleton
2014-06-16 9:45 ` Steffen Sledz
2014-06-16 10:59 ` Martin Jansa
2014-06-16 12:03 ` Steffen Sledz
2014-06-17 17:42 ` Martin Jansa
2014-06-16 16:36 ` akuster808 [this message]
2014-06-16 17:20 ` 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=539F1D15.8090304@gmail.com \
--to=akuster808@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=sledz@dresearch-fe.de \
/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