From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WiP] Plasma 5.21
Date: Mon, 25 Jan 2021 08:45:34 +0100 [thread overview]
Message-ID: <20210125074534.kxymk7GtwHvthmKgsMRSwXT_YTl-prfCjhKe9Wm9OaE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28205@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 411 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/28205#issuecomment-766617885
Comment:
> Maybe fix `KDE_SITE` so we don't end up requiring all of those substitutions? Not sure which one is simpler, especially now that you've done most of the work.
Srtictly speaking, we do not require these substitutions ever, since we do not ship unstable software.
next prev parent reply other threads:[~2021-01-25 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 22:24 [PR PATCH] " Johnnynator
2021-01-24 23:09 ` [PR REVIEW] " ericonr
2021-01-25 7:45 ` Johnnynator [this message]
2021-01-31 8:28 ` toluschr
2021-02-23 22:57 ` [PR PATCH] [Closed]: " Johnnynator
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=20210125074534.kxymk7GtwHvthmKgsMRSwXT_YTl-prfCjhKe9Wm9OaE@z \
--to=johnnynator@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).