All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: OpenEmbedded Development mailing list
	<openembedded-devel@lists.openembedded.org>
Subject: [meta-oe][PATCH] Correct spelling of "BBFILES_PRIORITY" in comments
Date: Tue, 22 Jul 2014 20:14:32 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.11.1407222013280.24982@localhost> (raw)


Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

diff --git a/meta-multimedia/conf/layer.conf b/meta-multimedia/conf/layer.conf
index 64a0a44..bfecb8c 100644
--- a/meta-multimedia/conf/layer.conf
+++ b/meta-multimedia/conf/layer.conf
@@ -4,7 +4,7 @@
 # search the directories from first to last as specified in BBPATH
 # Therefore if you want a given layer to be considered high priority
 # for the .inc and .conf etc. then consider it adding at the beginning
-# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
+# of BBPATH. For bblayers bitbake will use BBFILE_PRIORITY to resolve
 # the recipe contention so the order of directories in BBFILES does
 # not matter.

diff --git a/meta-oe/conf/layer.conf b/meta-oe/conf/layer.conf
index 2a5a428..9d7a60a 100644
--- a/meta-oe/conf/layer.conf
+++ b/meta-oe/conf/layer.conf
@@ -4,7 +4,7 @@
 # search the directories from first to last as specified in BBPATH
 # Therefore if you want a given layer to be considered high priority
 # for the .inc and .conf etc. then consider it adding at the beginning
-# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
+# of BBPATH. For bblayers bitbake will use BBFILE_PRIORITY to resolve
 # the recipe contention so the order of directories in BBFILES does
 # not matter.

diff --git a/meta-systemd/conf/layer.conf b/meta-systemd/conf/layer.conf
index f3fc45d..d8faf21 100644
--- a/meta-systemd/conf/layer.conf
+++ b/meta-systemd/conf/layer.conf
@@ -4,7 +4,7 @@
 # search the directories from first to last as specified in BBPATH
 # Therefore if you want a given layer to be considered high priority
 # for the .inc and .conf etc. then consider it adding at the beginning
-# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
+# of BBPATH. For bblayers bitbake will use BBFILE_PRIORITY to resolve
 # the recipe contention so the order of directories in BBFILES does
 # not matter.

diff --git a/toolchain-layer/conf/layer.conf b/toolchain-layer/conf/layer.conf
index ca81eb1..9289a8f 100644
--- a/toolchain-layer/conf/layer.conf
+++ b/toolchain-layer/conf/layer.conf
@@ -4,7 +4,7 @@
 # search the directories from first to last as specified in BBPATH
 # Therefore if you want a given layer to be considered high priority
 # for the .inc and .conf etc. then consider it adding at the beginning
-# of BBPATH. For bblayers bitbake will use BBFILES_PRIORITY to resolve
+# of BBPATH. For bblayers bitbake will use BBFILE_PRIORITY to resolve
 # the recipe contention so the order of directories in BBFILES does
 # not matter.


-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



             reply	other threads:[~2014-07-23  0:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23  0:14 Robert P. J. Day [this message]
2014-07-23 14:40 ` [meta-oe][PATCH] Correct spelling of "BBFILES_PRIORITY" in comments Martin Jansa

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=alpine.LFD.2.11.1407222013280.24982@localhost \
    --to=rpjday@crashcourse.ca \
    --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.