From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Remove deepin packages
Date: Fri, 13 Nov 2020 20:08:11 +0100 [thread overview]
Message-ID: <20201113190811.a6jaHwCXvNmpRoaLQsKcyu1zUDhOxBnlgTPz2inV4Ok@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26321@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
There's a merged pull request on the void-packages repository
Remove deepin packages
https://github.com/void-linux/void-packages/pull/26321
Description:
every update attempt of the deepin software stack resulted in some pain
or some kind of breakage somewhere. Since nobody else seems to be
intrested in updating it, remove it.
next prev parent reply other threads:[~2020-11-13 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 16:32 [PR PATCH] " Johnnynator
2020-11-13 19:08 ` Johnnynator [this message]
2021-02-05 21:49 ` gorkawien
2021-02-06 9:14 ` gorkawien
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=20201113190811.a6jaHwCXvNmpRoaLQsKcyu1zUDhOxBnlgTPz2inV4Ok@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).