From: Ruslan Bilovol <ruslan.bilovol@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6] Remove lost patches from oe-core
Date: Sat, 26 Jan 2019 14:57:54 +0200 [thread overview]
Message-ID: <1548507480-22805-1-git-send-email-ruslan.bilovol@gmail.com> (raw)
Working with recent oe-core I noticed that there are
patches not used by any recipe, which is confusing.
This is caused by mistakes in recipe upgrades, when
people remove patch from SRC_URI but forgets to
delete actual patch.
Instead of fixing only recipes I worked on,
I wrote a simple bash script which found all 6
lost patches in oe-core.
This patch series removes all of them
Ruslan Bilovol (6):
lttng: drop lost patch
bind: drop lost patch
dhcp: drop lost patch
connman: drop lost patch
subversion: drop lost patch
perl: drop lost patch
...0001-build-use-pkg-config-to-find-libxml2.patch | 54 ----------
...Add-prefixlen-to-iproute_default_function.patch | 63 -----------
.../dhcp/0008-tweak-to-support-external-bind.patch | 117 ---------------------
...kefile.SH-Pod-Simple-requires-Getopt-Long.patch | 34 ------
...erf.m4-Regex-modified-to-allow-D-in-paths.patch | 32 ------
...trfs-Remove-unnecessary-fs_info-parameter.patch | 116 --------------------
6 files changed, 416 deletions(-)
delete mode 100644 meta/recipes-connectivity/bind/bind/0001-build-use-pkg-config-to-find-libxml2.patch
delete mode 100644 meta/recipes-connectivity/connman/connman/0001-inet-Add-prefixlen-to-iproute_default_function.patch
delete mode 100644 meta/recipes-connectivity/dhcp/dhcp/0008-tweak-to-support-external-bind.patch
delete mode 100644 meta/recipes-devtools/perl/perl/0001-Makefile.SH-Pod-Simple-requires-Getopt-Long.patch
delete mode 100644 meta/recipes-devtools/subversion/subversion/serf.m4-Regex-modified-to-allow-D-in-paths.patch
delete mode 100644 meta/recipes-kernel/lttng/lttng-modules/0001-Fix-btrfs-Remove-unnecessary-fs_info-parameter.patch
--
1.9.1
next reply other threads:[~2019-01-26 12:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 12:57 Ruslan Bilovol [this message]
2019-01-26 12:57 ` [PATCH 1/6] lttng: drop lost patch Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 2/6] bind: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 3/6] dhcp: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 4/6] connman: " Ruslan Bilovol
2019-01-26 12:57 ` [PATCH 5/6] subversion: " Ruslan Bilovol
2019-01-26 12:58 ` [PATCH 6/6] perl: " Ruslan Bilovol
2019-01-30 23:19 ` [PATCH 0/6] Remove lost patches from oe-core Randy MacLeod
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=1548507480-22805-1-git-send-email-ruslan.bilovol@gmail.com \
--to=ruslan.bilovol@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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