From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] added recipe for libdbus-c++
Date: Tue, 15 Nov 2016 16:05:37 +0200 [thread overview]
Message-ID: <3b93c932-029e-42c0-06ef-c9d623534a93@linux.intel.com> (raw)
In-Reply-To: <20161115134607.13337-1-thilo.cestonaro@ts.fujitsu.com>
On 11/15/2016 03:46 PM, Thilo Cestonaro wrote:
> Signed-off-by: Thilo Cestonaro <thilo.cestonaro@ts.fujitsu.com>
> ---
> .../fix-missing-unistd.h-include.patch | 12 +
> .../remove-CXX_FOR_BUILD-stuff.patch | 257 +++++++++++++++++++++
> meta/recipes-core/dbus/libdbus-c++_0.9.0.bb | 24 ++
The whole thing should go to meta-openembedded (mailing list
openembedded-devel). Patches are missing description of what they are
for, and Upstream-Status, and Signed-off-by lines. Follow this please:
http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Alex
next prev parent reply other threads:[~2016-11-15 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 13:46 [PATCH] added recipe for libdbus-c++ Thilo Cestonaro
2016-11-15 14:05 ` Alexander Kanavin [this message]
2016-11-15 14:23 ` Burton, Ross
2016-11-15 15:27 ` thilo.cestonaro
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=3b93c932-029e-42c0-06ef-c9d623534a93@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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