From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: amend-recipes.inc
Date: Fri, 22 May 2009 17:32:05 -0400 [thread overview]
Message-ID: <4A1719D5.40605@cbnco.com> (raw)
In-Reply-To: <46AB4A4E-10FB-4BD2-8E6B-D6517A502FE8@mvista.com>
Christopher Larson wrote:
> I expect for now the best bet is to fix those base_set_filespath usages
> :) I'll see about fixing some this weekend, if I have the time.
OK, thanks for the explanation. It looks like the default FILESPATHPKG
already covers most of the cases for recipes that are using
base_set_filespath(). I guess that's probably by design. :)
Mike
next prev parent reply other threads:[~2009-05-22 21:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 18:20 amend-recipes.inc Christopher Larson
2009-05-22 20:35 ` amend-recipes.inc Michael Smith
2009-05-22 20:50 ` amend-recipes.inc Christopher Larson
2009-05-22 21:32 ` Michael Smith [this message]
2009-05-26 6:28 ` amend-recipes.inc Michael Smith
2009-05-26 6:34 ` [PATCH 1/4] Remove references to base_set_filespath() from recipes that don't need it Michael Smith
2009-05-26 6:34 ` [PATCH 2/4] Replace obsolete base_set_filespath() with FILESPATHPKG in some recipes Michael Smith
2009-05-26 6:34 ` [PATCH 3/4] glibc/eglibc: remove calls to obsolete base_set_filespath() Michael Smith
2009-05-26 6:34 ` [PATCH 4/4] uclibc: " Michael Smith
2009-05-30 16:42 ` Tom Rini
2009-05-30 16:42 ` [PATCH 3/4] glibc/eglibc: " Tom Rini
2009-05-30 16:42 ` [PATCH 2/4] Replace obsolete base_set_filespath() with FILESPATHPKG in some recipes Tom Rini
2009-05-30 0:48 ` [PATCH 1/4] Remove references to base_set_filespath()from recipes that don't need it Michael Smith
2009-05-30 5:29 ` Chris Larson
2009-05-30 17:32 ` Tom Rini
2009-05-30 16:42 ` [PATCH 1/4] Remove references to base_set_filespath() from " Tom Rini
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=4A1719D5.40605@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-devel@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.