From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Francois Perrad via buildroot <buildroot@buildroot.org>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH] package/ficl: downgrade to version 3.03
Date: Tue, 30 Dec 2025 13:49:46 +0100 [thread overview]
Message-ID: <20251230134946.3d737c29@windsurf> (raw)
In-Reply-To: <20251212084954.76257-1-francois.perrad@gadz.org>
Hello François,
Thanks for the patch.
On Fri, 12 Dec 2025 09:49:53 +0100
Francois Perrad via buildroot <buildroot@buildroot.org> wrote:
> diff --git a/package/ficl/0001-missing-include.patch b/package/ficl/0001-missing-include.patch
> new file mode 100644
> index 000000000..a52089623
> --- /dev/null
> +++ b/package/ficl/0001-missing-include.patch
> @@ -0,0 +1,26 @@
> +From 87c78eea2c4ac69c09947c8e49f8e8668640071c Mon Sep 17 00:00:00 2001
> +From: Francois Perrad <francois.perrad@gadz.org>
> +Date: Sun, 7 Dec 2025 10:15:27 +0100
> +Subject: [PATCH] missing include
> +
> +Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> +Upstream: upstream is dead
According to the link
https://sourceforge.net/p/ficl/news/2025/07/ficl4-is-retiring/ you
posted, upstream for version 3.x is not dead. So why don't you submit
this patch?
If upstream is really dead, should we remove this package instead?
Thanks!
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-12-30 12:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 8:49 [Buildroot] [PATCH] package/ficl: downgrade to version 3.03 Francois Perrad via buildroot
2025-12-30 12:49 ` 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=20251230134946.3d737c29@windsurf \
--to=buildroot@buildroot.org \
--cc=buildroot@busybox.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