From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 02/14] cli11: Refresh patch to fix fuzz
Date: Sun, 21 Jul 2019 09:39:07 -0700 [thread overview]
Message-ID: <20190721163919.32659-2-raj.khem@gmail.com> (raw)
In-Reply-To: <20190721163919.32659-1-raj.khem@gmail.com>
Fixes
cli11-1.8.0+gitAUTOINC+13becaddb6: Patch log indicates that patches do not apply cleanly. [patch-fuzz]
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
.../cli11/files/0001-Add-CLANG_TIDY-check.patch | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/meta-oe/recipes-support/cli11/files/0001-Add-CLANG_TIDY-check.patch b/meta-oe/recipes-support/cli11/files/0001-Add-CLANG_TIDY-check.patch
index bef3548a29..02b3c9bd7e 100644
--- a/meta-oe/recipes-support/cli11/files/0001-Add-CLANG_TIDY-check.patch
+++ b/meta-oe/recipes-support/cli11/files/0001-Add-CLANG_TIDY-check.patch
@@ -1,20 +1,21 @@
-From ef6310bc726a53ff6b45071633fa7b37224cae96 Mon Sep 17 00:00:00 2001
+From 902b251fd8d6408ee6623e7a92692948cf90187d Mon Sep 17 00:00:00 2001
From: Khem Raj <raj.khem@gmail.com>
Date: Tue, 12 Feb 2019 13:22:21 -0800
Subject: [PATCH] Add CLANG_TIDY check
Upstream-Status: Pending
Signed-off-by: Khem Raj <raj.khem@gmail.com>
+
---
CMakeLists.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
-index 79404b8..f68217d 100644
+index 7073a0b..2dd2c02 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
-@@ -39,7 +39,7 @@ if(CMAKE_PROJECT_NAME STREQUAL PROJECT_NAME)
- add_definitions(-Wall -Wextra -pedantic)
+@@ -60,7 +60,7 @@ if(CMAKE_PROJECT_NAME STREQUAL PROJECT_NAME)
+ endif()
endif()
- if(CMAKE_VERSION VERSION_GREATER 3.6)
@@ -22,6 +23,3 @@ index 79404b8..f68217d 100644
# Add clang-tidy if available
option(CLANG_TIDY_FIX "Perform fixes for Clang-Tidy" OFF)
find_program(
---
-2.20.1
-
--
2.22.0
next prev parent reply other threads:[~2019-07-21 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 16:39 [meta-oe][PATCH 01/14] recipes: Use BPN instead of PN in SRC_URIs Khem Raj
2019-07-21 16:39 ` Khem Raj [this message]
2019-07-21 16:39 ` [meta-webserver][PATCH 03/14] sthttpd: Use git SRC_URI instead of github archive Khem Raj
2019-07-21 16:39 ` [meta-networking][PATCH 04/14] arno-iptables-firewall: Switch to git fetcher Khem Raj
2019-07-21 16:39 ` [meta-networking][PATCH 05/14] firewalld: Update to 0.6.3->0.6.4 Khem Raj
2019-07-21 16:39 ` [meta-python][PATCH 06/14] python-matplotlib: Use git src_uri Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 07/14] mpv: Switch to using git fetcher Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 08/14] x11vnc: Switch to " Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 09/14] dumb-init: " Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 10/14] pam-plugin-ldapdb: Use " Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 11/14] libuv: Switch to using " Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 12/14] usbctl: Switch to " Khem Raj
2019-07-21 16:39 ` [meta-oe][PATCH 13/14] pmdk: Fix libdir which is multi-lib aware Khem Raj
2019-07-21 16:39 ` [meta-initramfs][PATCH 14/14] kexec-tools-klibc: Refresh patch with no code change Khem Raj
2019-07-23 8:09 ` Andrea Adami
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=20190721163919.32659-2-raj.khem@gmail.com \
--to=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox