From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/gawk: bump to version 5.2.2
Date: Tue, 18 Jul 2023 22:51:31 +0200 [thread overview]
Message-ID: <20230718225131.47f03dda@windsurf> (raw)
In-Reply-To: <20230715223616.847847-1-ju.o@free.fr>
On Sun, 16 Jul 2023 00:36:16 +0200
Julien Olivain <ju.o@free.fr> wrote:
> For news since 5.2.0, see:
> https://git.savannah.gnu.org/cgit/gawk.git/tree/NEWS?h=gawk-5.2.2
>
> For detailed change log, see:
> https://git.savannah.gnu.org/cgit/gawk.git/tree/ChangeLog?h=gawk-5.2.2
>
> This commit also removes the package patch, as it is included in
> upstream version 5.2.1, in:
> https://git.savannah.gnu.org/cgit/gawk.git/commit/?id=baab183439ff4e0c6b77d62156d447e61fc1dcfb
>
> The file .checkpackageignore is also updated to reflect this patch
> removal.
>
> The motivation of this bump is mainly the RISC-V fixes.
>
> Signed-off-by: Julien Olivain <ju.o@free.fr>
> ---
> .checkpackageignore | 1 -
> .../0001-Fix-a-bug-with-Node_elem_new.patch | 29 -------------------
> package/gawk/gawk.hash | 4 +--
> package/gawk/gawk.mk | 2 +-
> 4 files changed, 3 insertions(+), 33 deletions(-)
> delete mode 100644 package/gawk/0001-Fix-a-bug-with-Node_elem_new.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
prev parent reply other threads:[~2023-07-18 20:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 22:36 [Buildroot] [PATCH 1/1] package/gawk: bump to version 5.2.2 Julien Olivain
2023-07-18 20:51 ` 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=20230718225131.47f03dda@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--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 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.