From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel@lists.openembedded.org,
Armin Kuster <akuster808@gmail.com>,
Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-ruby][PATCH] ruby: explicitly disable dtrace support
Date: Tue, 05 May 2015 14:12:25 +0200 [thread overview]
Message-ID: <5548B3A9.40301@dresearch-fe.de> (raw)
In-Reply-To: <1430483441-4566-1-git-send-email-Martin.Jansa@gmail.com>
On 01.05.2015 14:30, Martin Jansa wrote:
> both 2.2.1 and 2.2.2 are failing on some hosts native builds with:
> ...
It would be really great if this patch could make it to the fido branch!
We are some of the mourners and cannot build fido at the moment. :(
--
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:[~2015-05-05 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 12:30 [meta-ruby][PATCH] ruby: explicitly disable dtrace support Martin Jansa
2015-05-02 0:08 ` akuster808
2015-05-02 8:11 ` Martin Jansa
2015-05-05 12:12 ` Steffen Sledz [this message]
2015-05-05 15:25 ` 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=5548B3A9.40301@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=akuster808@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