All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org, saul.wold@intel.com
Subject: [PATCH 1/1] kernel-yocto: export GUILT_BASE
Date: Tue,  8 May 2012 15:23:14 -0400	[thread overview]
Message-ID: <8afd5747802c4eb0e8296e440bd7366393595f8e.1336504721.git.bruce.ashfield@windriver.com> (raw)
In-Reply-To: <cover.1336504721.git.bruce.ashfield@windriver.com>
In-Reply-To: <cover.1336504721.git.bruce.ashfield@windriver.com>

One of the patch backends to linux-yocto is guilt, which normally
tracks patches under .git. But .git isn't something that can be
checked into a SCM and repeated. So it has been moved under meta/patches
and committed to the meta branch.

If devshell is used, GUILT_BASE isn't set, so patch manipulations will
fail. We export GUILT_BASE and point it at the meta directory when
devshell is invoked for linux-yocto.

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
---
 meta/classes/kernel-yocto.bbclass |    6 ++++++
 1 files changed, 6 insertions(+), 0 deletions(-)

diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index c6425b2..fb9dce1 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -290,4 +290,10 @@ do_kernel_link_vmlinux() {
 	ln -sf ../../../vmlinux
 }
 
+OE_TERMINAL_EXPORTS += "GUILT_BASE"
+python do_devshell () {
+    d.setVar("GUILT_BASE", "meta")
+    oe_terminal( d.getVar('SHELL', True), 'OpenEmbedded Developer Shell', d)
+}
+
 
-- 
1.7.0.4




  reply	other threads:[~2012-05-08 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 19:23 [PATCH 0/1] kernel-yocto: export GUILT_BASE Bruce Ashfield
2012-05-08 19:23 ` Bruce Ashfield [this message]
2012-05-09  6:51 ` Richard Purdie
2012-05-09 12:42   ` Bruce Ashfield
2012-05-09 13:08     ` Bruce Ashfield
2012-05-09 20:04       ` Richard Purdie
2012-05-09 20:14         ` 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=8afd5747802c4eb0e8296e440bd7366393595f8e.1336504721.git.bruce.ashfield@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=saul.wold@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.