All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Laszlo Papp <lpapp@kde.org>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH] Make the yocto layer dependent on oe-core
Date: Tue, 23 Jul 2013 07:30:24 -0700	[thread overview]
Message-ID: <51EE9380.5080307@linux.intel.com> (raw)
In-Reply-To: <1374577377-2614-1-git-send-email-lpapp@kde.org>


Laszlo,

Thanks for the patch, we have some standards for the patch commit, which 
can be found:

http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines

Key take away is to include the file name or recipe as the first item 
for example:

layer.conf: make the Yocto layer dependent on oe-core

Also this patch is actaully against Poky master and should go to the 
poky@yoctoproject.org.

Again thanks for your contribution, I look forward to a v2 and will pull 
it to the master_under_test branch.

Sau!


On 07/23/2013 04:02 AM, Laszlo Papp wrote:
> Signed-off-by: Laszlo Papp <lpapp@kde.org>
> ---
>   meta-yocto/conf/layer.conf | 5 +++++
>   1 file changed, 5 insertions(+)
>
> diff --git a/meta-yocto/conf/layer.conf b/meta-yocto/conf/layer.conf
> index e012f24..e326aad 100644
> --- a/meta-yocto/conf/layer.conf
> +++ b/meta-yocto/conf/layer.conf
> @@ -9,3 +9,8 @@ BBFILE_COLLECTIONS += "yocto"
>   BBFILE_PATTERN_yocto = "^${LAYERDIR}/"
>   BBFILE_PRIORITY_yocto = "5"
>
> +# This should only be incremented on significant changes that will
> +# cause compatibility issues with other layers
> +LAYERVERSION_yocto = "1"
> +
> +LAYERDEPENDS_yocto = "core"
>


      reply	other threads:[~2013-07-23 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 11:02 [PATCH] Make the yocto layer dependent on oe-core Laszlo Papp
2013-07-23 14:30 ` 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=51EE9380.5080307@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=lpapp@kde.org \
    --cc=yocto@yoctoproject.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.