Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 7/7] perl: add .pl, pm, pod, sh files to SSTATE_SCANE_FILES
Date: Thu, 15 Dec 2011 10:26:51 +0000	[thread overview]
Message-ID: <1323944813.24417.197.camel@phil-desktop> (raw)
In-Reply-To: <b52e93fb176d552e1334088af964dfbd38c0007d.1323911699.git.sgw@linux.intel.com>

On Wed, 2011-12-14 at 17:50 -0800, Saul Wold wrote:
> Signed-off-by: Saul Wold <sgw@linux.intel.com>
> ---
>  meta/recipes-devtools/perl/perl_5.14.2.bb |    5 ++++-
>  1 files changed, 4 insertions(+), 1 deletions(-)

This commit message is very terse.  What is SSTATE_SCAN[E]_FILES and why
do we want these things in it?

> +SSTATE_SCAN_FILES += "*.pm *.pod *.h *.pl *.sh"

p.






  reply	other threads:[~2011-12-15 10:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-15  1:50 [PATCH 0/7] SSTATE_SCAN_FILES Fix with non-gplv3 and World fixes Saul Wold
2011-12-15  1:50 ` [PATCH 1/7] qt-mobility: Fix QA error for debug files Saul Wold
2011-12-15  1:50 ` [PATCH 2/7] ed: Fix EXTRA_OECONF to ensure right compiler is found Saul Wold
2011-12-15  6:56   ` Khem Raj
2011-12-15  8:37     ` Saul Wold
2011-12-15 19:23       ` Saul Wold
2011-12-15  1:50 ` [PATCH 3/7] sstate: Add SSTATE_SCAN_FILES Saul Wold
2011-12-15  8:38   ` Saul Wold
2011-12-15 11:12   ` Richard Purdie
2011-12-15  1:50 ` [PATCH 4/7] icu: Add Makefile.inc to SSTATE_SCAN_FILES Saul Wold
2011-12-15  1:50 ` [PATCH 5/7] gmp: Add gmp.h " Saul Wold
2011-12-15  1:50 ` [PATCH 6/7] libtool-cross: Add libtool & libtoolize " Saul Wold
2011-12-15  1:50 ` [PATCH 7/7] perl: add .pl, pm, pod, sh files to SSTATE_SCANE_FILES Saul Wold
2011-12-15 10:26   ` Phil Blundell [this message]
2011-12-15 11:14     ` Richard Purdie
2011-12-15 14:46 ` [PATCH 0/7] SSTATE_SCAN_FILES Fix with non-gplv3 and World fixes Richard Purdie

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=1323944813.24417.197.camel@phil-desktop \
    --to=philb@gnu.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