From: LinArcX <LinArcX@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: neovim: update to 0.7.0.
Date: Sat, 23 Apr 2022 14:04:59 +0200 [thread overview]
Message-ID: <20220423120459.Jef6b1MXf0yR7FaA5jkMXlKfTLHPZ6OhElWz4AA-kyw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36704@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
New comment by LinArcX on void-packages repository
https://github.com/void-linux/void-packages/pull/36704#issuecomment-1107460347
Comment:
I have void-linux for more than 3 years, but recently i'm thinking more to switch to another distro,(that let me do whatever i want without any stupid limitations).
The main reason is that i still don't understand why maintainers of void insist on release versions of applications.
In my opinion, there's no single direction between "no-bug" and "high-quality" software with having "releases".
Stop this annoying policy and let people be more free.
next prev parent reply other threads:[~2022-04-23 12:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 12:48 [PR PATCH] " kartikynwa
2022-04-15 13:19 ` kartikynwa
2022-04-15 13:20 ` [PR PATCH] [Updated] " kartikynwa
2022-04-15 13:23 ` kartikynwa
2022-04-15 16:22 ` kartikynwa
2022-04-15 16:22 ` kartikynwa
2022-04-17 17:04 ` [PR PATCH] [Closed]: " kartikynwa
2022-04-17 18:00 ` kartikynwa
2022-04-18 4:32 ` kartikynwa
2022-04-18 8:54 ` Johnnynator
2022-04-18 9:47 ` kartikdc
2022-04-18 9:48 ` kartikdc
2022-04-18 11:13 ` kartikynwa
2022-04-18 11:17 ` kartikynwa
2022-04-18 19:22 ` gbrlsnchs
2022-04-20 4:01 ` kartikynwa
2022-04-20 15:30 ` LinArcX
2022-04-20 16:12 ` kartikynwa
2022-04-20 18:27 ` gbrlsnchs
2022-04-21 0:50 ` CameronNemo
2022-04-23 12:03 ` LinArcX
2022-04-23 12:04 ` LinArcX [this message]
2022-04-21 15:44 [PR PATCH] " siduck
2022-04-21 15:47 ` Chocimier
2022-04-21 15:55 ` siduck
2022-04-22 19:08 ` ram02z
2022-04-23 2:44 [PR PATCH] " thatboyjake
2022-04-23 2:49 ` classabbyamp
2022-04-23 3:12 ` thatboyjake
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=20220423120459.Jef6b1MXf0yR7FaA5jkMXlKfTLHPZ6OhElWz4AA-kyw@z \
--to=linarcx@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).