Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jukka Rissanen <jukka.rissanen@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] neard: Split recipe to two parts
Date: Fri, 03 May 2013 16:30:27 +0100	[thread overview]
Message-ID: <1367595027.5379.159.camel@ted> (raw)
In-Reply-To: <1367504436-9048-1-git-send-email-jukka.rissanen@linux.intel.com>

On Thu, 2013-05-02 at 17:20 +0300, Jukka Rissanen wrote:
> This way it is easier to override settings if needed.
> 
> Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>

This doesn't just split the recipe, it changes PV to use SRCREV instead
of SRCPV. That is plain wrong, it needs to use SRCPV if anything at all
(we could remove the line and pull 0.10 from the recipe name).

Cheers,

Richard




      reply	other threads:[~2013-05-03 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02 14:20 [PATCH] neard: Split recipe to two parts Jukka Rissanen
2013-05-03 15:30 ` Richard Purdie [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=1367595027.5379.159.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jukka.rissanen@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