Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] anydesk: update to 6.3.0, add armv7 support
Date: Sun, 24 Dec 2023 13:49:28 +0100	[thread overview]
Message-ID: <20231224124928.32H7GFkpjyuit8zE7jItVRFQ86D6Qc4iJJlatWGSqZk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47656@inbox.vuxu.org>

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

New review comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/47656#discussion_r1435820319

Comment:
with T&C like (it's not just a copyright licence) this the ones that apply are usually the ones that exist at the present moment, not what existed at build time, so for packages like this and chrome and discord I've moved them to this style.

  parent reply	other threads:[~2023-12-24 12:49 UTC|newest]

Thread overview: 88+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09  2:07 [PR PATCH] AnyDesk: update to v6.3.0 and added RPi3 armv7hf/armv7l support MechDR
2023-12-10  0:01 ` [PR REVIEW] " classabbyamp
2023-12-10  0:01 ` classabbyamp
2023-12-10  0:01 ` classabbyamp
2023-12-10  0:01 ` classabbyamp
2023-12-10  0:02 ` classabbyamp
2023-12-10  1:42 ` [PR PATCH] [Updated] " MechDR
2023-12-10  1:44 ` MechDR
2023-12-10  1:45 ` MechDR
2023-12-10  1:52 ` MechDR
2023-12-10  1:53 ` classabbyamp
2023-12-10  1:59 ` [PR REVIEW] " MechDR
2023-12-10  2:09 ` classabbyamp
2023-12-10  2:20 ` [PR PATCH] [Updated] " MechDR
2023-12-10  2:25 ` MechDR
2023-12-10  2:28 ` [PR REVIEW] " MechDR
2023-12-10  2:33 ` classabbyamp
2023-12-10  2:33 ` [PR REVIEW] " MechDR
2023-12-10  2:34 ` MechDR
2023-12-10  2:37 ` MechDR
2023-12-10  2:38 ` [PR REVIEW] " classabbyamp
2023-12-10  2:39 ` classabbyamp
2023-12-10  2:39 ` classabbyamp
2023-12-10  2:40 ` [PR REVIEW] " classabbyamp
2023-12-10  2:47 ` MechDR
2023-12-10  2:53 ` MechDR
2023-12-10  3:09 ` [PR REVIEW] " classabbyamp
2023-12-10  3:11 ` MechDR
2023-12-10  3:12 ` classabbyamp
2023-12-10  3:58 ` [PR PATCH] [Updated] " MechDR
2023-12-10  4:00 ` MechDR
2023-12-10  4:01 ` MechDR
2023-12-10  4:02 ` MechDR
2023-12-10  4:11 ` [PR REVIEW] " classabbyamp
2023-12-10  4:28 ` classabbyamp
2023-12-11 15:41 ` [PR PATCH] [Updated] " MechDR
2023-12-11 15:49 ` MechDR
2023-12-11 15:50 ` MechDR
2023-12-11 15:50 ` MechDR
2023-12-11 15:52 ` MechDR
2023-12-11 15:57 ` MechDR
2023-12-13 23:23 ` AnyDesk: update to 6.3.0, add armv7 support MechDR
2023-12-13 23:50 ` classabbyamp
2023-12-14  0:58 ` MechDR
2023-12-14  0:59 ` classabbyamp
2023-12-14  1:02 ` MechDR
2023-12-14  1:03 ` MechDR
2023-12-14  1:08 ` classabbyamp
2023-12-14  1:11 ` MechDR
2023-12-14  1:12 ` [PR PATCH] [Updated] " MechDR
2023-12-14  1:54 ` MechDR
2023-12-14  1:55 ` MechDR
2023-12-14  1:56 ` MechDR
2023-12-14 23:54 ` [PR PATCH] [Updated] " MechDR
2023-12-15  1:58 ` MechDR
2023-12-15  1:59 ` MechDR
2023-12-22 19:37 ` 0x5c
2023-12-23 16:58 ` MechDR
2023-12-23 17:03 ` classabbyamp
2023-12-23 17:23 ` MechDR
2023-12-23 17:25 ` 0x5c
2023-12-23 17:28 ` classabbyamp
2023-12-23 18:38 ` MechDR
2023-12-23 18:38 ` MechDR
2023-12-23 18:45 ` 0x5c
2023-12-23 19:32 ` MechDR
2023-12-23 19:44 ` [PR PATCH] [Updated] " MechDR
2023-12-23 19:46 ` MechDR
2023-12-23 22:51 ` MechDR
2023-12-23 22:51 ` MechDR
2023-12-23 22:54 ` [PR PATCH] [Updated] anydesk: " MechDR
2023-12-23 22:56 ` MechDR
2023-12-23 23:08 ` classabbyamp
2023-12-23 23:54 ` MechDR
2023-12-24  2:52 ` 0x5c
2023-12-24  3:06 ` MechDR
2023-12-24 12:24 ` [PR REVIEW] " ahesford
2023-12-24 12:31 ` ahesford
2023-12-24 12:49 ` classabbyamp [this message]
2023-12-24 12:57 ` [PR REVIEW] " ahesford
2023-12-25  8:08 ` MechDR
2023-12-25  8:08 ` MechDR
2023-12-25  8:09 ` MechDR
2023-12-25  8:12 ` MechDR
2023-12-25  9:48 ` [PR PATCH] [Updated] " MechDR
2024-01-21  2:48 ` MechDR
2024-02-15  5:32 ` classabbyamp
2024-02-15  5:32 ` [PR PATCH] [Closed]: " classabbyamp

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=20231224124928.32H7GFkpjyuit8zE7jItVRFQ86D6Qc4iJJlatWGSqZk@z \
    --to=classabbyamp@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).