From: Justin Bronder <jsbronder@cold-front.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: cppzmq: 4.2.3 update
Date: Fri, 2 Mar 2018 15:54:57 -0500 [thread overview]
Message-ID: <20180302205457.GL23655@lasswell> (raw)
In-Reply-To: <20180302203140.6397-1-jsbronder@cold-front.org>
Please ignore this, I pasted in the wrong sha. I'll fix and resubmit.
On 02/03/18 15:31 -0500, Justin Bronder 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..b660b69da 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}"
> +SRCREV = "3226b8ebddd9c6c738ba42986822c26418a49afb"
> +PV = "4.2.3+git${SRCPV}"
>
> SRC_URI = "git://github.com/zeromq/cppzmq.git"
>
> --
> 2.13.6
>
--
Justin Bronder
next prev parent reply other threads:[~2018-03-02 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 20:31 [meta-oe][PATCH v2 1/2] cppzmq: 4.2.3 update Justin Bronder
2018-03-02 20:31 ` [meta-oe][PATCH v2 2/2] zeromq: " Justin Bronder
2018-03-02 20:54 ` Justin Bronder [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-26 20:16 [meta-oe][PATCH 1/2] cppzmq: " Justin Bronder
2018-02-28 5:51 ` akuster808
2018-02-28 15:27 ` Justin Bronder
2018-03-01 15:36 ` [meta-oe][PATCH 1/2] " Andreas Oberritter
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=20180302205457.GL23655@lasswell \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox