Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] git: fix sstate relocation for git-native
Date: Mon, 05 Sep 2011 20:20:05 +0100	[thread overview]
Message-ID: <1315250405.1243.5.camel@ted> (raw)
In-Reply-To: <cae9b6aa44f57843cf9a9575b85ef33350b0a41e.1315237572.git.paul.eggleton@linux.intel.com>

On Mon, 2011-09-05 at 16:47 +0100, Paul Eggleton wrote:
> Create a wrapper for git to set GIT_EXEC_PATH and GIT_TEMPLATE_DIR so
> that git-native is relocatable.
> 
> Fixes specific example given in [YOCTO #1137]
> 
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
> ---
>  meta/recipes-devtools/git/git.inc        |    6 ++++++
>  meta/recipes-devtools/git/git_1.7.5.1.bb |    2 +-
>  2 files changed, 7 insertions(+), 1 deletions(-)

Merged to master, thanks.

Richard




      reply	other threads:[~2011-09-05 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-05 15:47 [PATCH 0/1] fix sstate relocation for git-native Paul Eggleton
2011-09-05 15:47 ` [PATCH 1/1] git: " Paul Eggleton
2011-09-05 19:20   ` Richard Purdie [this message]

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=1315250405.1243.5.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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