From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
Cc: "Eric Le Bihan" <eric.le.bihan.dev@free.fr>,
"J. Neuschäfer" <j.neuschaefer@gmx.net>
Subject: Re: [Buildroot] [PATCH v2 0/4] Optionally build some skarnet.org packages as multicall binaries
Date: Thu, 15 Aug 2024 10:58:24 +0200 [thread overview]
Message-ID: <20240815105824.37914b70@windsurf> (raw)
In-Reply-To: <20240811-s6-multicall-v2-0-14249fd20cbd@gmx.net>
On Sun, 11 Aug 2024 12:01:10 +0200
J. Neuschäfer via buildroot <buildroot@buildroot.org> wrote:
> J. Neuschäfer (4):
> package/execline: Add option to build multicall binary
> package/s6-portable-utils: Add option to build multicall binary
> package/s6-linux-utils: Add option to build multicall binary
> DEVELOPERS: Add skarnet.org packages to J. Neuschäfer's entry
Thanks, series applied to next!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-15 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 10:01 [Buildroot] [PATCH v2 0/4] Optionally build some skarnet.org packages as multicall binaries J. Neuschäfer via buildroot
2024-08-11 10:01 ` [Buildroot] [PATCH v2 1/4] package/execline: Add option to build multicall binary J. Neuschäfer via buildroot
2024-08-11 10:01 ` [Buildroot] [PATCH v2 2/4] package/s6-portable-utils: " J. Neuschäfer via buildroot
2024-08-11 10:01 ` [Buildroot] [PATCH v2 3/4] package/s6-linux-utils: " J. Neuschäfer via buildroot
2024-08-11 10:01 ` [Buildroot] [PATCH v2 4/4] DEVELOPERS: Add skarnet.org packages to J. Neuschäfer's entry J. Neuschäfer via buildroot
2024-08-15 8:58 ` Thomas Petazzoni via buildroot [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=20240815105824.37914b70@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=j.neuschaefer@gmx.net \
--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