From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Fixes for bitbake wrapper script
Date: Sat, 31 Mar 2012 16:45:56 +0100 [thread overview]
Message-ID: <2542745.0CB1lCEMpW@helios> (raw)
In-Reply-To: <cover.1332848153.git.paul.eggleton@linux.intel.com>
On Tuesday 27 March 2012 12:50:07 Paul Eggleton wrote:
> Andreas, if you could review these that would be much appreciated.
>
>
> The following changes since commit 644b7503c37fd73730dd3d7841463b158b8934ed:
>
> guile: Deal with hardcoded path issues (2012-03-27 00:28:41 +0100)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/builddir
>
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paul
> e/builddir
>
> Paul Eggleton (3):
> scripts/bitbake: try harder to check if pseudo exists
> scripts/bitbake: allow switching between build directories
> scripts/bitbake: add/fix some comments
>
> scripts/bitbake | 43 ++++++++++++++++++++++++++++++++-----------
> 1 files changed, 32 insertions(+), 11 deletions(-)
FYI I've rebased this patch on top of Mark's recent bitbake wrapper script
changes that are now in master.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-03-31 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 11:50 [PATCH 0/3] Fixes for bitbake wrapper script Paul Eggleton
2012-03-27 11:50 ` [PATCH 1/3] scripts/bitbake: try harder to check if pseudo exists Paul Eggleton
2012-03-27 13:08 ` Andreas Oberritter
2012-03-27 13:14 ` Paul Eggleton
2012-03-27 11:50 ` [PATCH 2/3] scripts/bitbake: allow switching between build directories Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter
2012-03-27 11:50 ` [PATCH 3/3] scripts/bitbake: add/fix some comments Paul Eggleton
2012-03-27 13:09 ` Andreas Oberritter
2012-03-31 15:45 ` Paul Eggleton [this message]
2012-04-03 23:33 ` [PATCH 0/3] Fixes for bitbake wrapper script Saul Wold
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=2542745.0CB1lCEMpW@helios \
--to=paul.eggleton@linux.intel.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 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.