From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Min Xu <xuminready@gmail.com>
Cc: James Hilliard <james.hilliard1@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/shadowsocks-libev: remove this package. No longer maintained.
Date: Sat, 23 Jul 2022 18:32:14 +0200 [thread overview]
Message-ID: <20220723183214.5d1a74e6@windsurf> (raw)
In-Reply-To: <20220519074438.462-1-xuminready@gmail.com>
Hello Min,
On Thu, 19 May 2022 00:44:38 -0700
Min Xu <xuminready@gmail.com> wrote:
> Signed-off-by: Min Xu <xuminready@gmail.com>
> ---
> DEVELOPERS | 3 -
> package/Config.in | 1 -
> ...-pkg-config-to-find-netfilter_conntr.patch | 62 -------------
> .../0002-fix-maybe-uninitialized-errors.patch | 93 -------------------
> package/shadowsocks-libev/Config.in | 34 -------
> .../shadowsocks-libev/shadowsocks-libev.hash | 7 --
> .../shadowsocks-libev/shadowsocks-libev.mk | 27 ------
> 7 files changed, 227 deletions(-)
> delete mode 100644 package/shadowsocks-libev/0001-configure.ac-use-pkg-config-to-find-netfilter_conntr.patch
> delete mode 100644 package/shadowsocks-libev/0002-fix-maybe-uninitialized-errors.patch
> delete mode 100644 package/shadowsocks-libev/Config.in
> delete mode 100644 package/shadowsocks-libev/shadowsocks-libev.hash
> delete mode 100644 package/shadowsocks-libev/shadowsocks-libev.mk
Thanks for your patch. As there has been recent commits (25 days ago)
to shadowsocks-libev, and James has expressed that the package could
potentially be useful, I have instead:
(1) Fixed the recurring build issue:
https://git.buildroot.org/buildroot/commit/?id=380d9ad503d552dac2817d3a487f681530030752
(2) Removed you from the DEVELOPERS to make sure you no longer receive
e-mail notifications:
https://git.buildroot.org/buildroot/commit/?id=f704ec56f85b4aebb75a76fd7dbd9db800bf1b9e
Note that this commit is for now only in our master branch, but we
also test older branches. So you may continue to receive e-mail
notifications for a little while, until the update to the
DEVELOPERS file is propagated to older branches.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-23 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 7:44 [Buildroot] [PATCH 1/1] package/shadowsocks-libev: remove this package. No longer maintained Min Xu
2022-05-19 9:29 ` James Hilliard
2022-05-20 6:24 ` xu min
2022-05-20 6:32 ` James Hilliard
2022-07-23 16:32 ` 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=20220723183214.5d1a74e6@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=xuminready@gmail.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