All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: Justin Bronder <jsbronder@cold-front.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 1/2] cppzmq: 4.2.3 update
Date: Thu, 1 Mar 2018 16:36:36 +0100	[thread overview]
Message-ID: <20180301163636.494655bb@t460p> (raw)
In-Reply-To: <20180226201605.29261-1-jsbronder@cold-front.org>

Hi Justin,

On Mon, 26 Feb 2018 15:16:04 -0500
Justin Bronder <jsbronder@cold-front.org> wrote:

> Signed-off-by: Justin Bronder <jsbronder@cold-front.org>
> ---
>  meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> index a64745c94..9e8ad5151 100644
> --- a/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> +++ b/meta-oe/recipes-connectivity/zeromq/cppzmq_git.bb
> @@ -4,8 +4,8 @@ LICENSE = "MIT"
>  LIC_FILES_CHKSUM = "file://LICENSE;md5=db174eaf7b55a34a7c89551197f66e94"
>  DEPENDS = "zeromq"
>  
> -SRCREV = "68a7b09cfce01c4c279fba2cf91686fcfc566848"
> -PV = "4.1.5+git${SRCPV}"
> +PV = "4.2.3"
> +SRCREV = "v${PV}"

we usually don't use tags in SRCREV, because tags may change over time, and
therefore bitbake has to query the server each time it parses the recipe, IIRC.

Regards,
Andreas


  parent reply	other threads:[~2018-03-01 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 20:16 [meta-oe][PATCH 1/2] cppzmq: 4.2.3 update Justin Bronder
2018-02-26 20:16 ` [meta-oe][PATCH 2/2] zeromq: " Justin Bronder
2018-02-28  5:52   ` akuster808
2018-02-28 15:30     ` Justin Bronder
2018-02-28  5:51 ` [meta-oe][PATCH 1/2] cppzmq: " akuster808
2018-02-28 15:27   ` Justin Bronder
2018-03-01 15:36 ` Andreas Oberritter [this message]
2018-03-01 15:47   ` Justin Bronder
2018-03-01 16:14     ` Andreas Oberritter
2018-03-02 20:32       ` Justin Bronder

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=20180301163636.494655bb@t460p \
    --to=obi@opendreambox.org \
    --cc=jsbronder@cold-front.org \
    --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.