From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] package: add host-coreutils (branch yem/host-coreutils)
Date: Mon, 6 Jan 2020 21:47:04 +0100 [thread overview]
Message-ID: <20200106214704.0413d5dc@windsurf> (raw)
In-Reply-To: <cover.1576701539.git.yann.morin.1998@free.fr>
Hello,
On Wed, 18 Dec 2019 21:39:04 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> Yann E. MORIN (5):
> package/coreutils: introduce a host variant
> core/dependencies: check if we need to build our own host-coreutils
> package/systemd: add dependency on host-coreutils
> package/libselinux: add dependency on host-coreutils for ln --relative
> package/libsepol: add dependency on host-coreutils for ln --relative
Thanks, I've applied to master!
One thing that would be nice is to check if
package/coreutils/0001-fix-for-dummy-man-usage.patch is still needed,
and if it is, what we can do about it. It's annoying to have AUTORECONF
= YES and GETTEXTIZE = YES just for this patch.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-01-06 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 20:39 [Buildroot] [PATCH 0/5] package: add host-coreutils (branch yem/host-coreutils) Yann E. MORIN
2019-12-18 20:39 ` [Buildroot] [PATCH 1/5] package/coreutils: introduce a host variant Yann E. MORIN
2019-12-18 20:39 ` [Buildroot] [PATCH 2/5] core/dependencies: check if we need to build our own host-coreutils Yann E. MORIN
2019-12-18 20:39 ` [Buildroot] [PATCH 3/5] package/systemd: add dependency on host-coreutils Yann E. MORIN
2019-12-18 20:39 ` [Buildroot] [PATCH 4/5] package/libselinux: add dependency on host-coreutils for ln --relative Yann E. MORIN
2019-12-18 20:39 ` [Buildroot] [PATCH 5/5] package/libsepol: " Yann E. MORIN
2020-01-06 20:47 ` 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=20200106214704.0413d5dc@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 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.