From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
"Yann E . MORIN" <yann.morin.1998@free.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/nut: bump to version 2.8.2
Date: Mon, 8 Apr 2024 23:09:35 +0200 [thread overview]
Message-ID: <20240408230935.170ec78e@windsurf> (raw)
In-Reply-To: <20240404195346.1434611-1-fontaine.fabrice@gmail.com>
On Thu, 4 Apr 2024 21:53:46 +0200
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:
> Drop patches (already in version) and so also drop autoreconf
>
> https://github.com/networkupstools/nut/releases/tag/v2.8.2
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> ...iler_family.m4-fix-cross-compilation.patch | 55 ---------
> ...hon.m4-allow-overriding-of-PYTHON-2-.patch | 106 ------------------
> package/nut/nut.hash | 4 +-
> package/nut/nut.mk | 5 +-
> 4 files changed, 4 insertions(+), 166 deletions(-)
> delete mode 100644 package/nut/0001-m4-nut_compiler_family.m4-fix-cross-compilation.patch
> delete mode 100644 package/nut/0002-m4-nut_check_python.m4-allow-overriding-of-PYTHON-2-.patch
Applied to master, thanks.
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
next prev parent reply other threads:[~2024-04-08 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 19:53 [Buildroot] [PATCH 1/1] package/nut: bump to version 2.8.2 Fabrice Fontaine
2024-04-08 21:09 ` Thomas Petazzoni via buildroot [this message]
[not found] <20240404195346.1434611-1-fontaine.fabrice__24633.80233837$1712260531$gmane$org@gmail.com>
2024-04-05 15:45 ` Bernd Kuhls
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=20240408230935.170ec78e@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=fontaine.fabrice@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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