From: SpidFightFR <SpidFightFR@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] PrismLauncher: update to 7.1.
Date: Sat, 17 Jun 2023 18:29:50 +0200 [thread overview]
Message-ID: <20230617162950.IcknNHk74emiaa194KGNa-KdkfRK9zyU3IreJpTbuL0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44326@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 441 bytes --]
New review comment by SpidFightFR on void-packages repository
https://github.com/void-linux/void-packages/pull/44326#discussion_r1233089369
Comment:
But it builds Polymc alongside Prism, it causes errors during building process… With all the changes brought to Prism and the drama (and the eventual death) of Polymc, it’s fair to assume that people are aware of the change. Otherwise, they’d still be on multimc.
but fair enough.
next prev parent reply other threads:[~2023-06-17 16:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 9:22 [PR PATCH] PrismLauncher: update to 7.0 SpidFightFR
2023-06-09 18:22 ` classabbyamp
2023-06-10 6:20 ` SpidFightFR
2023-06-10 7:10 ` SpidFightFR
2023-06-10 8:40 ` classabbyamp
2023-06-10 13:15 ` SpidFightFR
2023-06-10 13:15 ` SpidFightFR
2023-06-11 9:25 ` oynqr
2023-06-11 10:02 ` SpidFightFR
2023-06-11 11:17 ` classabbyamp
2023-06-17 11:24 ` [PR PATCH] [Updated] " SpidFightFR
2023-06-17 11:31 ` PrismLauncher: update to 7.1 SpidFightFR
2023-06-17 14:41 ` [PR PATCH] [Updated] " SpidFightFR
2023-06-17 14:42 ` SpidFightFR
2023-06-17 14:42 ` SpidFightFR
2023-06-17 15:18 ` [PR REVIEW] " classabbyamp
2023-06-17 16:29 ` SpidFightFR [this message]
2023-06-17 16:30 ` SpidFightFR
2023-06-17 16:35 ` classabbyamp
2023-06-17 17:04 ` SpidFightFR
2023-06-17 17:20 ` classabbyamp
2023-06-18 6:24 ` [PR PATCH] [Updated] " SpidFightFR
2023-06-18 7:09 ` [PR PATCH] [Merged]: " classabbyamp
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=20230617162950.IcknNHk74emiaa194KGNa-KdkfRK9zyU3IreJpTbuL0@z \
--to=spidfightfr@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).