From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] kernel-yocto: split meta data generation from patching phase
Date: Tue, 17 Mar 2015 09:50:09 -0400 [thread overview]
Message-ID: <55083111.9090301@windriver.com> (raw)
In-Reply-To: <CAJTo0LbffFs6r_GkzF7CTUP+1yxrUydwq6RxRZTgJhbZbhiYSA@mail.gmail.com>
On 15-03-17 09:49 AM, Burton, Ross wrote:
>
> On 17 March 2015 at 14:21, Bruce Ashfield <bruce.ashfield@windriver.com
> <mailto:bruce.ashfield@windriver.com>> wrote:
>
> It was. The extra output only goes to the logs, and it is helpful
> in diagnosing problems.
>
> .. and yes, the obvious follow up is that I should have put that
> in the commit message!
>
>
> It looked a bit like debugging changes, thought I'd check.
Always better to be safe. It's not like we all haven't left those
in before :)
Bruce
>
> Cheers,
> Ross
next prev parent reply other threads:[~2015-03-17 13:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 17:27 [PATCH 0/5] kernel: consolidated pull request Bruce Ashfield
2015-03-16 17:27 ` [PATCH 1/5] kern-tools: fix iterative configuration runs Bruce Ashfield
2015-03-16 17:27 ` [PATCH 2/5] kernel-yocto: split meta data generation from patching phase Bruce Ashfield
2015-03-17 6:52 ` Burton, Ross
2015-03-17 12:21 ` Bruce Ashfield
2015-03-17 13:49 ` Burton, Ross
2015-03-17 13:50 ` Bruce Ashfield [this message]
2015-03-17 13:51 ` Burton, Ross
2015-03-16 17:27 ` [PATCH 3/5] linux-yocto/3.19: integrate korg -stable update Bruce Ashfield
2015-03-16 17:27 ` [PATCH 4/5] perf: drop PR Bruce Ashfield
2015-03-17 7:01 ` Burton, Ross
2015-03-17 12:20 ` Bruce Ashfield
2015-03-17 13:48 ` Burton, Ross
2015-03-17 13:50 ` Bruce Ashfield
2015-03-17 13:52 ` Burton, Ross
2015-03-16 17:27 ` [PATCH 5/5] perf: add bash to RDEPENDS Bruce Ashfield
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=55083111.9090301@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.