From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perale via buildroot <buildroot@buildroot.org>
Cc: Thomas Perale <thomas.perale@mind.be>
Subject: Re: [Buildroot] [PATCH] package/softether: fix various build errors
Date: Wed, 9 Jul 2025 23:13:27 +0200 [thread overview]
Message-ID: <20250709231327.0ed2fa35@windsurf> (raw)
In-Reply-To: <20250709200737.408235-1-thomas.perale@mind.be>
On Wed, 9 Jul 2025 22:07:36 +0200
Thomas Perale via buildroot <buildroot@buildroot.org> wrote:
> This packages hasn't been bumped since 2019 & no-one is following it on
> the DEVELOPERS list. Given the increasing number of patches and
> difficulty to maintain it, I think it's a good candidate to be removed.
Totally agree.
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:[~2025-07-09 21:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 20:07 [Buildroot] [PATCH] package/softether: fix various build errors Thomas Perale via buildroot
2025-07-09 21:13 ` Thomas Petazzoni via buildroot [this message]
2025-08-10 13:50 ` Romain Naour via buildroot
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=20250709231327.0ed2fa35@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--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