From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/exfatprogs: bump to version 1.0.3
Date: Fri, 15 May 2020 22:08:25 +0200 [thread overview]
Message-ID: <20200515220825.7e6bfe73@windsurf.home> (raw)
In-Reply-To: <20200513032859.18478-1-james.hilliard1@gmail.com>
On Tue, 12 May 2020 21:28:59 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Drop patches that are now upstream.
>
> We don't need to autoreconf since we are using a release tarball.
>
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ---
> ...rogs-add-missing-include-sys-types.h.patch | 49 ------
> ...PRIu64-PRIx64-to-printf-64-bit-types.patch | 144 ------------------
> ...k-fix-node-may-be-used-uninitialized.patch | 63 --------
> .../0004-fsck-Zero-init-using-memset.patch | 37 -----
> package/exfatprogs/exfatprogs.hash | 2 +-
> package/exfatprogs/exfatprogs.mk | 5 +-
> 6 files changed, 3 insertions(+), 297 deletions(-)
> delete mode 100644 package/exfatprogs/0001-exfatprogs-add-missing-include-sys-types.h.patch
> delete mode 100644 package/exfatprogs/0002-mkfs-fsck-use-PRIu64-PRIx64-to-printf-64-bit-types.patch
> delete mode 100644 package/exfatprogs/0003-fsck-fix-node-may-be-used-uninitialized.patch
> delete mode 100644 package/exfatprogs/0004-fsck-Zero-init-using-memset.patch
We normally don't take version bumps in master, but I looked through
the changes between 1.0.2 and 1.0.3 and all of them are fixes, and this
patch allows to drop a number of patches. So, I've applied to master.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-05-15 20:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 3:28 [Buildroot] [PATCH 1/1] package/exfatprogs: bump to version 1.0.3 James Hilliard
2020-05-15 20:08 ` Thomas Petazzoni [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=20200515220825.7e6bfe73@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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