From: Trevor Woerner <twoerner@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: State of bitbake world, Failed tasks 2016-03-16
Date: Fri, 18 Mar 2016 20:23:11 -0400 [thread overview]
Message-ID: <20160319002311.GA1738@linux-yxv0> (raw)
In-Reply-To: <20160317144357.GB2553@jama>
On Thu 2016-03-17 @ 03:43:57 PM, Martin Jansa wrote:
> c278358 metadata-revs: provide more information
I think the general consensus was to not accept patch c278358 since it
affected the layout of a file that was expected to be processed by scripts.
> e2bf30c buildhistory.bbclass: metadata-revs show repo parent
But I *think* everyone was okay with this one?
next prev parent reply other threads:[~2016-03-19 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 14:43 State of bitbake world, Failed tasks 2016-03-16 Martin Jansa
2016-03-19 0:23 ` Trevor Woerner [this message]
2016-03-20 21:26 ` Paul Eggleton
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=20160319002311.GA1738@linux-yxv0 \
--to=twoerner@gmail.com \
--cc=martin.jansa@gmail.com \
--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