From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte via buildroot" <buildroot@buildroot.org>
Cc: "James Hilliard" <james.hilliard1@gmail.com>,
"Raphaël Mélotte" <raphael.melotte@mind.be>
Subject: Re: [Buildroot] [PATCH v2 4/5] package/mupdf: bump to version 1.23.9
Date: Sat, 13 Jul 2024 22:36:21 +0200 [thread overview]
Message-ID: <20240713223621.37f3d317@windsurf> (raw)
In-Reply-To: <20240607163208.1445715-4-raphael.melotte@mind.be>
On Fri, 7 Jun 2024 18:32:05 +0200
Raphaël Mélotte via buildroot <buildroot@buildroot.org> wrote:
> From: James Hilliard <james.hilliard1@gmail.com>
>
> Drop patch which is now upstream.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> [bump to 1.23.9]
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
> ---
> ...issing-limits.h-include-for-UINT_MAX.patch | 70 -------------------
> package/mupdf/mupdf.hash | 4 +-
> package/mupdf/mupdf.mk | 2 +-
> 3 files changed, 3 insertions(+), 73 deletions(-)
> delete mode 100644 package/mupdf/0001-Add-missing-limits.h-include-for-UINT_MAX.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-07-13 20:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 21:13 [Buildroot] [PATCH 0/5] package/python-pymupdf: bump to version 1.23.22 Raphaël Mélotte via buildroot
2024-02-16 21:13 ` [Buildroot] [PATCH 1/5] package: python-pymupdf: add missing python-zlib dependency Raphaël Mélotte via buildroot
2024-06-07 16:32 ` [Buildroot] [PATCH v2 " Raphaël Mélotte via buildroot
2024-06-07 16:32 ` [Buildroot] [PATCH v2 2/5] support/testing: add new test for python-pymupdf Raphaël Mélotte via buildroot
2024-07-13 20:35 ` Thomas Petazzoni via buildroot
2024-08-12 9:51 ` Peter Korsgaard
2024-06-07 16:32 ` [Buildroot] [PATCH v2 3/5] package/mupdf: fix building shared libraries Raphaël Mélotte via buildroot
2024-07-13 20:36 ` Thomas Petazzoni via buildroot
2024-08-12 9:14 ` Peter Korsgaard
2024-06-07 16:32 ` [Buildroot] [PATCH v2 4/5] package/mupdf: bump to version 1.23.9 Raphaël Mélotte via buildroot
2024-07-13 20:36 ` Thomas Petazzoni via buildroot [this message]
2024-06-07 16:32 ` [Buildroot] [PATCH v2 5/5] package/python-pymupdf: bump to version 1.23.22 Raphaël Mélotte via buildroot
2024-07-13 20:38 ` Thomas Petazzoni via buildroot
2024-07-13 20:34 ` [Buildroot] [PATCH v2 1/5] package: python-pymupdf: add missing python-zlib dependency Thomas Petazzoni via buildroot
2024-08-12 9:51 ` Peter Korsgaard
2024-02-16 21:13 ` [Buildroot] [PATCH 2/5] support/testing: add new test for python-pymupdf Raphaël Mélotte via buildroot
2024-02-16 21:13 ` [Buildroot] [PATCH 3/5] package/mupdf: fix building shared libraries Raphaël Mélotte via buildroot
2024-04-01 20:06 ` Arnout Vandecappelle via buildroot
2024-06-07 16:44 ` Raphaël Mélotte via buildroot
2024-02-16 21:13 ` [Buildroot] [PATCH 4/5] package/mupdf: bump to version 1.23.9 Raphaël Mélotte via buildroot
2024-02-16 21:13 ` [Buildroot] [PATCH 5/5] package/python-pymupdf: bump to version 1.23.22 Raphaël Mélotte via buildroot
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=20240713223621.37f3d317@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=raphael.melotte@mind.be \
--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