From: blloyd <blloyd@familyhonor.net>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] devshell should make finding source and build artifacts easy
Date: Thu, 31 Oct 2013 03:02:01 -0500 [thread overview]
Message-ID: <cover.1383206227.git.blloyd@familyhonor.net> (raw)
Make finding sources and build artificts easy from a developer shell, while not affecting normal shells.
Also cleans up EOL issue from first attempt at patch.
The following changes since commit 523f2a9ea970713fb775bc48f84b67420b1106a0:
cross-canadian: Improve comment (2013-10-30 18:01:34 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib blloyd/devshell
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=blloyd/devshell
blloyd (2):
Allow passthrough of important placement variables when using devshell
Removed trailing whitespace added with last commit
meta/classes/devshell.bbclass | 10 ++++++++++
1 file changed, 10 insertions(+)
--
1.8.1.4
next reply other threads:[~2013-10-31 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 8:02 blloyd [this message]
2013-10-31 8:02 ` [PATCH 1/2] Allow passthrough of important placement variables when using devshell blloyd
2013-11-01 11:04 ` Richard Purdie
2013-11-01 11:04 ` Richard Purdie
2013-10-31 8:02 ` [PATCH 2/2] Removed trailing whitespace added with last commit blloyd
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=cover.1383206227.git.blloyd@familyhonor.net \
--to=blloyd@familyhonor.net \
--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