From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: onivim2-0.5.5
Date: Mon, 24 May 2021 01:51:12 +0200 [thread overview]
Message-ID: <20210523235112.fQNxzP7_jy9zQNsTNAXPamPwRIl_9blnRW17my82r04@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31076@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
New comment by kawaiiamber on void-packages repository
https://github.com/void-linux/void-packages/pull/31076#issuecomment-846645911
Comment:
Oh wow. I wasn't aware that onivim2 also copies the bad licensing practices from vs code, too. It's a shame that in order to distribute this software you must use a one and a half year old version at the very least. Onivim seemed pretty cool, it's a shame upstream seems to be anti-freedom in that sense, though. I don't want to make a template for a version over a year old, so I guess I'll update the template to be restricted when I get back home - RIP
next prev parent reply other threads:[~2021-05-23 23:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-23 8:32 [PR PATCH] " kawaiiamber
2021-05-23 11:55 ` FollieHiyuki
2021-05-23 16:17 ` F0Xde
2021-05-23 16:33 ` ericonr
2021-05-23 17:04 ` FollieHiyuki
2021-05-23 23:51 ` kawaiiamber [this message]
2021-05-23 23:54 ` kawaiiamber
2021-05-23 23:55 ` kawaiiamber
2021-05-24 0:00 ` kawaiiamber
2021-05-24 11:38 ` kawaiiamber
2021-05-24 11:45 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-24 11:46 ` kawaiiamber
2021-05-24 11:58 ` kawaiiamber
2021-05-24 15:49 ` FollieHiyuki
2021-05-25 0:32 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-25 0:33 ` kawaiiamber
2021-05-25 0:35 ` [PR PATCH] [Updated] " kawaiiamber
2021-05-25 0:41 ` kawaiiamber
2022-05-20 2:12 ` github-actions
2022-06-18 2:12 ` [PR PATCH] [Closed]: " github-actions
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=20210523235112.fQNxzP7_jy9zQNsTNAXPamPwRIl_9blnRW17my82r04@z \
--to=kawaiiamber@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).