From: Steffen Sledz <sledz@dresearch-fe.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [meta-oe][daisy][PATCH] live555: fix fetch problem
Date: Mon, 16 Jun 2014 11:45:12 +0200 [thread overview]
Message-ID: <539EBCA8.3000709@dresearch-fe.de> (raw)
In-Reply-To: <6076930.voh3DpIb8j@peggleto-mobl5.ger.corp.intel.com>
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).
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2014-06-16 9:45 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 [this message]
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
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=539EBCA8.3000709@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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