From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Better communication
Date: Mon, 04 Sep 2023 11:56:55 +0200 [thread overview]
Message-ID: <20230904095655.CW9BGnZyVnwJoQybxjD2whgMj1p2RYwtpfRyNa6Ao0A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45892@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/45892#issuecomment-1704965946
Comment:
> It's awesome that some chatter in a non officially logged IRC chat can create a lot of chaos /s, the communication process failed and it wont be changed magically, this will not be the last time. Also this wonderful new precedent will be used in the future, like how a bad action was used to justify the crypto removal PR. Even if after the fact it was "accepted" that it wasn't good. I gave this one a heart because they provided an example [#44422 (comment)](https://github.com/void-linux/void-packages/pull/44422#issuecomment-1659081991)
>
> Also the claim in the PR opening comment is false, not all the PRs referenced where dead or tiny unimportant projects. #43702 #44133 I am so glad that was so well inspected before approval. /s
> Any how thank you for insulting me directly, its so nice lol! Your doing a good job adding to the list of quality interactions with the void package maintainers /s
Awesome another made up bad interaction you can fit your narrative.
> So Void is a not a general purpose operating system and is instead a playpen for only the stuff a few people find interesting?
Merging packages that are going to be build on void linux build servers and are in the official repository are merged at the void teams discretion. If they don't get actively maintained anymore, if they need rebuilds due to dependencies, they will fall back on people who are regular contributors. What a shocker, every single open source project and linux distribution works like that.
next prev parent reply other threads:[~2023-09-04 9:56 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-03 5:23 [ISSUE] " Yorizuka
2023-09-03 5:43 ` classabbyamp
2023-09-03 6:00 ` Yorizuka
2023-09-03 6:00 ` Yorizuka
2023-09-03 6:29 ` Yorizuka
2023-09-03 11:11 ` Duncaen
2023-09-03 16:20 ` Yorizuka
2023-09-03 17:07 ` Duncaen
2023-09-03 17:07 ` Duncaen
2023-09-03 17:08 ` Duncaen
2023-09-03 17:18 ` Duncaen
2023-09-03 17:20 ` Duncaen
2023-09-03 17:20 ` Duncaen
2023-09-03 17:24 ` Duncaen
2023-09-03 17:30 ` Duncaen
2023-09-03 17:31 ` Duncaen
2023-09-03 18:54 ` Duncaen
2023-09-03 18:55 ` Duncaen
2023-09-03 20:18 ` Yorizuka
2023-09-03 20:38 ` Eloitor
2023-09-03 21:22 ` Yorizuka
2023-09-04 0:13 ` Duncaen
2023-09-04 0:14 ` Duncaen
2023-09-04 0:15 ` Duncaen
2023-09-04 0:16 ` Duncaen
2023-09-04 0:18 ` Duncaen
2023-09-04 7:20 ` Yorizuka
2023-09-04 7:21 ` Yorizuka
2023-09-04 7:22 ` Yorizuka
2023-09-04 7:27 ` Yorizuka
2023-09-04 7:35 ` Yorizuka
2023-09-04 7:37 ` Yorizuka
2023-09-04 9:54 ` Duncaen
2023-09-04 9:56 ` Duncaen [this message]
2023-09-04 10:01 ` Duncaen
2023-09-04 10:05 ` Yorizuka
2023-09-04 10:07 ` Yorizuka
2023-09-04 10:07 ` Yorizuka
2023-09-04 10:17 ` Duncaen
2023-09-04 10:24 ` Yorizuka
2023-09-04 11:10 ` Yorizuka
2023-09-04 11:12 ` Yorizuka
2023-09-04 11:17 ` Yorizuka
2023-09-04 11:25 ` Yorizuka
2023-09-04 11:39 ` Yorizuka
2023-09-04 23:35 ` 0x5c
2023-09-05 0:49 ` Yorizuka
2023-09-05 0:53 ` Yorizuka
2023-09-05 1:09 ` Yorizuka
2023-09-16 15:52 ` [ISSUE] [CLOSED] " ahesford
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=20230904095655.CW9BGnZyVnwJoQybxjD2whgMj1p2RYwtpfRyNa6Ao0A@z \
--to=duncaen@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).