Github messages for voidlinux
 help / color / mirror / Atom feed
From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: element-web-1.11.8
Date: Mon, 03 Oct 2022 03:33:08 +0200	[thread overview]
Message-ID: <20221003013308.U2weTYNwq7xW9eSoWlsO-ady0-lIox2FnL68SWqytnw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39554@inbox.vuxu.org>

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

New comment by TinfoilSubmarine on void-packages repository

https://github.com/void-linux/void-packages/pull/39554#issuecomment-1264815588

Comment:
These are all good points, and several are ones I've run into before that have stopped me from packaging something, or at least from submitting a template I've been using for my own machines.

I will say that I would consider this PR to be an exception to that reasoning since we have several different matrix servers packaged and it would be nice for convenience sake to be able to install a client as well.

  parent reply	other threads:[~2022-10-03  1:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 21:17 [PR PATCH] New package: element-web-1.11.8 (and move element/riot-desktop as subpackages) TinfoilSubmarine
2022-09-30 23:02 ` TinfoilSubmarine
2022-09-30 23:05 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-09-30 23:43 ` New package: element-web-1.11.8 paper42
2022-10-03  1:31 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-10-03  1:33 ` TinfoilSubmarine [this message]
2022-10-14 13:00 ` TinfoilSubmarine
2022-10-27 12:31 ` [PR PATCH] [Updated] New package: element-web-1.11.10 TinfoilSubmarine
2022-11-01 13:28 ` [PR PATCH] [Updated] New package: element-web-1.11.12 TinfoilSubmarine
2023-01-20 15:01 ` [PR PATCH] [Closed]: New package: element-web-1.11.13 TinfoilSubmarine

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=20221003013308.U2weTYNwq7xW9eSoWlsO-ady0-lIox2FnL68SWqytnw@z \
    --to=tinfoilsubmarine@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).