From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: bitbake.conf: Tidy up a few comment typoes; no functional changes.
Date: Tue, 03 Jul 2012 10:56:25 -0700 [thread overview]
Message-ID: <4FF33249.3030804@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1207010531450.30586@oneiric>
On 07/01/2012 02:32 AM, Robert P. J. Day wrote:
>
> Signed-off-by: Robert P. J. Day<rpjday@crashcourse.ca>
>
> ---
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 9377ee6..0a177c8 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -368,7 +368,7 @@ DEPLOY_DIR_TOOLS = "${DEPLOY_DIR}/tools"
> PKGDATA_DIR = "${TMPDIR}/pkgdata/${MULTIMACH_TARGET_SYS}"
>
> ##################################################################
> -# SDK variables,
> +# SDK variables.
> ##################################################################
>
> SDK_NAME_PREFIX ?= "oecore"
> @@ -395,9 +395,9 @@ IMAGE_LINK_NAME = "${IMAGE_BASENAME}-${MACHINE}"
> # This option allows for a percentage overage of the actual image size rather than a
> # fixed extra space, this is space needed for initial startup and basic operations.
> IMAGE_OVERHEAD_FACTOR ?= "1.3"
> -# This option allow for adding addition space in K above and beyond what the
> +# This option allows for adding additional space in K above and beyond what the
> # IMAGE_OVERHEAD_FACTOR might add. This space is for additional packages, user data, ...
> -# To set a fixed size then overrideing IMAGE_ROOTFS_SIZE with the max size one wants
> +# To set a fixed size then overriding IMAGE_ROOTFS_SIZE with the max size one wants
> # should do the trick
> IMAGE_ROOTFS_EXTRA_SPACE ?= "0"
>
> @@ -418,7 +418,7 @@ CCACHE ??= ""
> # Disable ccache explicitly if CCACHE is null since gcc may be a symlink
> # of ccache some distributions (e.g., Fedora 17).
> export CCACHE_DISABLE ??= "${@[0,1][d.getVar('CCACHE', True) == '']}"
> -# Assign CCACHE_DIR a default vaule to fix a bug of ccache 3.1.7,
> +# Assign CCACHE_DIR a default value to fix a bug of ccache 3.1.7,
> # since it would always create CCACHE_DIR/.ccache even if
> # CCACHE_DISABLE = 1.
> export CCACHE_DIR ??= "${@os.getenv('HOME')}"
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-07-03 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 9:32 bitbake.conf: Tidy up a few comment typoes; no functional changes Robert P. J. Day
2012-07-03 17:56 ` 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=4FF33249.3030804@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