From: Jonathan Rajotte Julien <Jonathan.rajotte-julien@efficios.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Babeltrace - Backport fix to fido (as-needed.inc: add babeltrace exception)
Date: Fri, 6 Jan 2017 16:41:49 -0500 [thread overview]
Message-ID: <2bc5740d-4245-a666-d21a-e89940ebe2fc@efficios.com> (raw)
In-Reply-To: <2b581c5f-7199-7a0b-5288-cae9e8309a73@efficios.com>
Hi,
Reposting to mailing list since I was not allowed without a subscription.
Both Alexander Kanavin (Babeltrace recipe maintainer) and Richard Purdie
were CC on the initial message.
Original Message
--
Hi,
The following commit [1] is present since Jethro but the issue is also
present in Fido.
Since the commit apply cleanly, could it be possible to backport it to Fido?
Cheers
[1]
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=3006cb260004a7bd88cfd4ea3e2cbcac600347bc
--
Jonathan R. Julien
Efficios
next parent reply other threads:[~2017-01-06 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2b581c5f-7199-7a0b-5288-cae9e8309a73@efficios.com>
2017-01-06 21:41 ` Jonathan Rajotte Julien [this message]
2017-01-09 18:39 ` Babeltrace - Backport fix to fido (as-needed.inc: add babeltrace exception) Khem Raj
2017-01-11 14:39 ` 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=2bc5740d-4245-a666-d21a-e89940ebe2fc@efficios.com \
--to=jonathan.rajotte-julien@efficios.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