From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] PolyMC upstream hijacked
Date: Tue, 18 Oct 2022 00:26:17 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40012@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
New issue by fanyx on void-packages repository
https://github.com/void-linux/void-packages/issues/40012
Description:
Freenode-esque hostile takeover of the project is presently unfolding[1][2].
[1]: https://floss.social/@modrinth/109185261746948078
[2]: https://github.com/PolyMC/PolyMC/commit/ccf282593dcdbe189c99b81b8bc90cb203aed3ee
might want to remove the update file from the repo asap until the situation resolves.
next reply other threads:[~2022-10-17 22:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 22:26 fanyx [this message]
2022-10-17 23:24 ` paper42
2022-10-17 23:28 ` paper42
2022-10-18 9:50 ` [ISSUE] [CLOSED] " fanyx
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40012@inbox.vuxu.org \
--to=fanyx@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).