All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Mingyu <wangmy@fujitsu.com>
To: <openembedded-devel@lists.openembedded.org>
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-oe] [PATCH] pegtl: upgrade 3.2.1 -> 3.2.5
Date: Thu, 14 Apr 2022 10:32:30 +0800	[thread overview]
Message-ID: <1649903550-17752-4-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1649903550-17752-1-git-send-email-wangmy@fujitsu.com>

Changelog:
==========
Added missing include for fallback demangle() implementations.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../recipes-extended/pegtl/{pegtl_3.2.1.bb => pegtl_3.2.5.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-oe/recipes-extended/pegtl/{pegtl_3.2.1.bb => pegtl_3.2.5.bb} (85%)

diff --git a/meta-oe/recipes-extended/pegtl/pegtl_3.2.1.bb b/meta-oe/recipes-extended/pegtl/pegtl_3.2.5.bb
similarity index 85%
rename from meta-oe/recipes-extended/pegtl/pegtl_3.2.1.bb
rename to meta-oe/recipes-extended/pegtl/pegtl_3.2.5.bb
index f0ae229414..b4e0d17b37 100644
--- a/meta-oe/recipes-extended/pegtl/pegtl_3.2.1.bb
+++ b/meta-oe/recipes-extended/pegtl/pegtl_3.2.5.bb
@@ -3,8 +3,8 @@ HOMEPAGE="https://github.com/taocpp/PEGTL"
 LICENSE="MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=5b6701671289d12b7ffa69138832c006"
 
-SRC_URI = "git://github.com/taocpp/PEGTL.git;protocol=https;branch=main"
-SRCREV = "6d03c8decc22b4ddd51115e2170e0e82413c7104"
+SRC_URI = "git://github.com/taocpp/PEGTL.git;protocol=https;branch=3.x"
+SRCREV = "eeba7fa1180655bd683be620cc31be35607442ca"
 
 inherit cmake
 
-- 
2.25.1



      parent reply	other threads:[~2022-04-14 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  2:32 [oe] [meta-oe] [PATCH] pam-plugin-ldapdb: upgrade 1.3 -> 1.3.1 Wang Mingyu
2022-04-14  2:32 ` [oe] [meta-oe] [PATCH] pax-utils: upgrade 1.2.2 -> 1.3.3 Wang Mingyu
2022-04-14  2:32 ` [oe] [meta-oe] [PATCH] pcsc-tools: upgrade 1.5.8 -> 1.6.0 Wang Mingyu
2022-04-14  2:32 ` Wang Mingyu [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=1649903550-17752-4-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.com \
    --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.