Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [wic][PATCH] wic: try to find bitbake using find_executable API
Date: Mon, 20 Apr 2015 19:59:18 +0300	[thread overview]
Message-ID: <20150420165918.GA14044@linux.intel.com> (raw)
In-Reply-To: <5534F189.3010901@balister.org>

On Mon, Apr 20, 2015 at 08:31:05AM -0400, Philip Balister wrote:
> I forgot to cc the list. Unfortunately, this led to the commit going in
> with the reference to oe-classic.
> 
> Please people, get your terminology correct. The word soup in the wold
> is insane.
> 

My bad. I've received your e-mail, but didn't have time to send the fix during weekend.
Today I've noticed that my patch was already merged.

--
Regards,
Ed


  reply	other threads:[~2015-04-20 16:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55311968.50404@balister.org>
2015-04-20 12:31 ` [wic][PATCH] wic: try to find bitbake using find_executable API Philip Balister
2015-04-20 16:59   ` Ed Bartosh [this message]
2015-04-17 13:19 Ed Bartosh

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=20150420165918.GA14044@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philip@balister.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