From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "J. Neuschäfer via buildroot" <buildroot@buildroot.org>
Cc: "J. Neuschäfer" <j.neuschaefer@gmx.net>,
"Dick Olsson" <hi@senzilla.io>,
"Eric Le Bihan" <eric.le.bihan.dev@free.fr>
Subject: Re: [Buildroot] [PATCH v2 0/3] Update skarnet.org packages
Date: Sun, 18 May 2025 16:42:13 +0200 [thread overview]
Message-ID: <20250518164213.78c9bd60@windsurf> (raw)
In-Reply-To: <20250414-ska-bump-v2-0-efb0a276750d@gmx.net>
On Mon, 14 Apr 2025 13:19:31 +0200
J. Neuschäfer via buildroot <buildroot@buildroot.org> wrote:
> J. Neuschäfer (3):
> skarnet.org packages: remove --prefix=/
> skarnet.org packages: bump to new versions (October 2024)
> package/execline: remove -D_GNU_SOURCE
Thanks, series applied! There were two packages for which the license
file had changed (copyright year change) but that you had forgotten to
update. I took care of that. Thanks again!
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:[~2025-05-18 14:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 11:19 [Buildroot] [PATCH v2 0/3] Update skarnet.org packages J. Neuschäfer via buildroot
2025-04-14 11:19 ` [Buildroot] [PATCH v2 1/3] skarnet.org packages: remove --prefix=/ J. Neuschäfer via buildroot
2025-04-14 11:19 ` [Buildroot] [PATCH v2 2/3] skarnet.org packages: bump to new versions (October 2024) J. Neuschäfer via buildroot
2025-04-14 11:19 ` [Buildroot] [PATCH v2 3/3] package/execline: remove -D_GNU_SOURCE J. Neuschäfer via buildroot
2025-06-04 18:27 ` Arnout Vandecappelle via buildroot
2025-05-18 14:42 ` 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=20250518164213.78c9bd60@windsurf \
--to=buildroot@buildroot.org \
--cc=eric.le.bihan.dev@free.fr \
--cc=hi@senzilla.io \
--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