Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] package.bbclass: Allow overriding of debugedit base path
Date: Tue, 17 Jul 2012 09:06:00 -0700	[thread overview]
Message-ID: <50058D68.1090505@linux.intel.com> (raw)
In-Reply-To: <cover.1342038551.git.peter.seebach@windriver.com>

On 07/11/2012 01:31 PM, Peter Seebach wrote:
> As before, only with the prettier and smaller change RP suggested. This
> provides a mechanism for making the existing debugedit that gets done
> from package.bbclass work for prebuilt binaries with debug paths that
> aren't related directly to the build environment.
>
> The following changes since commit 20405bdab18b7a2b101f818e72863d289d5945e4:
>    Bruce Ashfield (1):
>          linux-yocto/3.0: perf scripting support
>
> are available in the git repository at:
>
>    git://git.yoctoproject.org/poky-contrib seebs/debugsrc
>    http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/debugsrc
>
> Peter Seebach (1):
>    package.bbclass: Allow overriding of debugedit starting path
>
>   meta/classes/package.bbclass |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
Merged into OE-Core

Thanks
	Sau!




      parent reply	other threads:[~2012-07-17 16:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 20:31 [PATCH 0/1] package.bbclass: Allow overriding of debugedit base path Peter Seebach
2012-07-11 20:31 ` [PATCH 1/1] package.bbclass: Allow overriding of debugedit starting path Peter Seebach
2012-07-17 16:06 ` Saul Wold [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=50058D68.1090505@linux.intel.com \
    --to=sgw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox