From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Julien Olivain <ju.o@free.fr>
Cc: Lance Fredrickson <lancethepants@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] boot/syslinux: Fix building syslinux with GCC 14.x
Date: Wed, 10 Jul 2024 22:28:35 +0200 [thread overview]
Message-ID: <20240710222835.5c329cc7@windsurf> (raw)
In-Reply-To: <38e42162ab203dcbf1b02124a5d6a402@free.fr>
On Sun, 23 Jun 2024 10:10:59 +0000
Julien Olivain <ju.o@free.fr> wrote:
> Even syslinux had no release since 2014, its mailing list is still more
> or less operating: https://www.syslinux.org/archives/
> The patch could be sent on that list, in case the project gets a new
> maintainer or get forked by somebody else...
I agree, but there's been no commit since 6 years in the Git repo, no
release in 10 years, so I tend to agree also with the fact that
upstream is dead. It's pretty crazy that no alternative
upstream/maintainer has emerged for this project (though its code base
is not amazing, so not very encouraging project to take over the
maintenance of).
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
next prev parent reply other threads:[~2024-07-10 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 3:38 [Buildroot] [PATCH 1/1] boot/syslinux: Fix building syslinux with GCC 14.x Lance Fredrickson
2024-06-23 10:10 ` Julien Olivain
2024-07-10 20:28 ` Thomas Petazzoni via buildroot [this message]
2024-07-10 20:27 ` Thomas Petazzoni via buildroot
2024-07-28 7:08 ` Peter Korsgaard
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=20240710222835.5c329cc7@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=lancethepants@gmail.com \
--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 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.