From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad <fperrad@gmail.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH 1/5] package/open62541: bump to version 1.3.1
Date: Wed, 20 Jul 2022 22:58:54 +0200 [thread overview]
Message-ID: <20220720225854.5d025455@windsurf> (raw)
In-Reply-To: <20220615161753.2580142-1-francois.perrad@gadz.org>
On Wed, 15 Jun 2022 18:17:49 +0200
Francois Perrad <fperrad@gmail.com> wrote:
> remove patches
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> ...sts.txt-project-only-contains-C-code.patch | 27 ----------
> ...eLists.txt-fix-build-without-threads.patch | 37 -------------
> ...licit-cast-to-avoid-compiler-warning.patch | 25 ---------
> ...4-CMakeLists.txt-add-UA_FORCE_WERROR.patch | 54 -------------------
> package/open62541/open62541.hash | 2 +-
> package/open62541/open62541.mk | 2 +-
> 6 files changed, 2 insertions(+), 145 deletions(-)
> delete mode 100644 package/open62541/0001-CMakeLists.txt-project-only-contains-C-code.patch
> delete mode 100644 package/open62541/0002-arch-posix-CMakeLists.txt-fix-build-without-threads.patch
> delete mode 100644 package/open62541/0003-fix-core-Explicit-cast-to-avoid-compiler-warning.patch
> delete mode 100644 package/open62541/0004-CMakeLists.txt-add-UA_FORCE_WERROR.patch
"remove patches" is really a short justification, so I have expanded
that to explain why each patch is dropped. Could you try to do that for
your next version bump with patches dropped?
Applied to master with this change!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-20 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 16:17 [Buildroot] [PATCH 1/5] package/open62541: bump to version 1.3.1 Francois Perrad
2022-06-15 16:17 ` [Buildroot] [PATCH 2/5] package/open62541: more options Francois Perrad
2022-07-20 20:58 ` Thomas Petazzoni via buildroot
2022-06-15 16:17 ` [Buildroot] [PATCH 3/5] package/open62541: more PubSub options Francois Perrad
2022-07-20 20:59 ` Thomas Petazzoni via buildroot
2022-06-15 16:17 ` [Buildroot] [PATCH 4/5] package/open62541: add encryption support Francois Perrad
2022-07-20 21:01 ` Thomas Petazzoni via buildroot
2022-06-15 16:17 ` [Buildroot] [PATCH 5/5] package/open62541: refactor choice UA_NAMESPACE with a proper default Francois Perrad
2022-07-20 21:02 ` Thomas Petazzoni via buildroot
2022-07-20 20:58 ` Thomas Petazzoni via buildroot [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=20220720225854.5d025455@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.net \
--cc=fperrad@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
/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