From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] package/busybox: version bump to 1.30.1
Date: Mon, 25 Mar 2019 19:10:42 +0100 [thread overview]
Message-ID: <20190325191042.0279e322@windsurf> (raw)
In-Reply-To: <20190325162819.13056-1-jared.bents@rockwellcollins.com>
On Mon, 25 Mar 2019 11:28:19 -0500
jared.bents at rockwellcollins.com wrote:
> From: Jared Bents <jared.bents@rockwellcollins.com>
>
> Update from version 1.29.3 to 1.30.1. The new version
> includes the removed patches.
>
> Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com>
> ---
> ...l.sh-don-t-clobber-dangling-symlinks.patch | 38 -----
> ...tions-are-indeed-4-byte-closes-11506.patch | 137 ------------------
> ...HCP_SUBNET-ensure-it-is-4-bytes-long.patch | 58 --------
> package/busybox/busybox.hash | 4 +-
> package/busybox/busybox.mk | 2 +-
> 5 files changed, 3 insertions(+), 236 deletions(-)
> delete mode 100644 package/busybox/0003-install.sh-don-t-clobber-dangling-symlinks.patch
> delete mode 100644 package/busybox/0004-udhcpc-check-that-4-byte-options-are-indeed-4-byte-closes-11506.patch
> delete mode 100644 package/busybox/0005-udhcpc-when-decoding-DHCP_SUBNET-ensure-it-is-4-bytes-long.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-25 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 16:28 [Buildroot] [PATCH v1 1/1] package/busybox: version bump to 1.30.1 jared.bents at rockwellcollins.com
2019-03-25 18:10 ` 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=20190325191042.0279e322@windsurf \
--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