From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] systemd: bump to v240
Date: Wed, 26 Dec 2018 21:54:48 +0100 [thread overview]
Message-ID: <20181226215448.0eede5a3@windsurf.home> (raw)
In-Reply-To: <20181223011208.43478-1-aduskett@gmail.com>
Hello,
On Sat, 22 Dec 2018 20:12:08 -0500, aduskett at gmail.com wrote:
> From: Adam Duskett <Aduskett@gmail.com>
>
> In addition:
> - Remove unused option -Dkill-path.
> (See commit 9a85778412fa3e3f8d4561064131ba69f3259b28)
>
> - Change option -Dmyhostname to -Dnss-myhostname.
>
> - Remove patches from upstream.
>
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> ---
> .../0002-install-don-t-use-ln-relative.patch | 2 +-
> ...-whether-struct-statx-is-defined-in-.patch | 111 ------------------
> ...x-stat.h-check-with-other-checks-and.patch | 77 ------------
> ...we-have-enough-space-for-the-DHCP6-o.patch | 30 -----
> ...build-fix-detection-of-Werror-shadow.patch | 34 ------
> package/systemd/systemd.hash | 2 +-
> package/systemd/systemd.mk | 7 +-
> 7 files changed, 5 insertions(+), 258 deletions(-)
> delete mode 100644 package/systemd/0003-build-sys-Detect-whether-struct-statx-is-defined-in-.patch
> delete mode 100644 package/systemd/0004-meson-unify-linux-stat.h-check-with-other-checks-and.patch
> delete mode 100644 package/systemd/0005-dhcp6-make-sure-we-have-enough-space-for-the-DHCP6-o.patch
> delete mode 100644 package/systemd/0006-meson.build-fix-detection-of-Werror-shadow.patch
Applied to master. However, you forgot to update the hash of the README
file, which is listed in systemd.hash. Please make sure to run "make
legal-info" before sending a version bump of a package. Thanks!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-26 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 1:12 [Buildroot] [PATCH 1/1] systemd: bump to v240 aduskett at gmail.com
2018-12-23 22:19 ` Jérémy Rosen
2018-12-26 20:54 ` 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=20181226215448.0eede5a3@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