Github messages for voidlinux
 help / color / mirror / Atom feed
From: Arzte <Arzte@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package Request: Discord
Date: Mon, 16 Mar 2020 19:40:25 +0100	[thread overview]
Message-ID: <20200316184025.2BrT42255uMW-A7Suh3-urD7nn0MGSppORPtmNjfS5g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20107@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 925 bytes --]

New comment by Arzte on void-packages repository

https://github.com/void-linux/void-packages/issues/20107#issuecomment-599698263

Comment:
I went back and looked at the support tickets I made asking about distributing Discord, (I'm the original author, however the original pr seems to no longer exist on github) 
Last communication I had with them over 4 years ago looks to be them asking the following: 
<img width="510" alt="Screen Shot 2020-03-16 at 2 36 00 PM" src="https://user-images.githubusercontent.com/7450443/76789573-7c362c80-6793-11ea-9480-fdac0778d767.png">

I would take this to mean Void Linux never "officially" got permission to distribute the Discord binaries, and if this is desired, Someone would have to ask their support desk for permission again.

(To my knowledge they're quite friendly to this, it's just a matter of asking, and clarifying that mirroring and the such is fine and allowed)


  parent reply	other threads:[~2020-03-16 18:40 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  1:57 [ISSUE] " Frick-David
2020-03-16  2:01 ` abenson
2020-03-16  2:06 ` abenson
2020-03-16  2:26 ` bobertlo
2020-03-16  7:57 ` Frick-David
2020-03-16  8:24 ` kyunal
2020-03-16 10:21 ` Duncaen
2020-03-16 10:25 ` kyunal
2020-03-16 10:27 ` Duncaen
2020-03-16 10:28 ` Duncaen
2020-03-16 18:37 ` Arzte
2020-03-16 18:38 ` Arzte
2020-03-16 18:40 ` Arzte [this message]
2020-03-16 18:41 ` Arzte
2020-03-16 18:44 ` Arzte
2020-03-16 18:50 ` Arzte
2020-03-16 18:50 ` Arzte
2020-03-16 20:07 ` kyunal
2020-03-16 20:22 ` Duncaen
2020-03-16 20:25 ` kyunal
2020-03-17 20:00 ` Frick-David
2020-03-20  5:32 ` Frick-David
2020-03-20  6:01 ` Frick-David
2020-03-20  6:04 ` Frick-David
2020-03-20  6:04 ` Frick-David
2020-03-20 16:15 ` wundrweapon
2020-03-20 16:16 ` wundrweapon
2020-03-20 17:02 ` bobertlo
2020-03-20 17:04 ` bobertlo
2020-03-20 21:04 ` Arzte
2020-03-20 21:23 ` Duncaen
2020-03-20 21:24 ` Duncaen
2020-03-20 21:24 ` Duncaen
2020-03-23 13:42 ` Frick-David
2020-04-18 13:51 ` rc-05
2021-01-08 22:24 ` kawaiiamber
2021-01-08 22:30 ` Duncaen
2022-04-16  2:02 ` github-actions
2022-04-30  2:13 ` [ISSUE] [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=20200316184025.2BrT42255uMW-A7Suh3-urD7nn0MGSppORPtmNjfS5g@z \
    --to=arzte@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).