From: Spacur <Spacur@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: libpurple-discord-0.9.2023.02.15.git.4a09188
Date: Sat, 24 Jun 2023 23:15:27 +0200 [thread overview]
Message-ID: <20230624211527.kA6zyk8O3u1EDT94NmhAUIB7QM1oVjOS66NO3gQdIoE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44608@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
New comment by Spacur on void-packages repository
https://github.com/void-linux/void-packages/pull/44608#issuecomment-1605733153
Comment:
Hi there @abenson,
I understand this and left a note regarding this in the notes to inquire further. Given the author has never provided a version ever for this project (And it appears that the author expects users to use the build at the latest commit as the software ready to use by the general public shown by the author pointing to the nightly build for the download) is there any exceptions to this rule? I have additionally used this software at the latest build for several months without issue on 3 different operating systems. https://github.com/EionRobb/purple-discord
If there can be no exceptions whatsoever, I will raise this with the package author instead to see if they can create an official release and hopefully re-raise this pull request per procedure at a later date.
next prev parent reply other threads:[~2023-06-24 21:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 12:30 [PR PATCH] " Spacur
2023-06-24 18:21 ` abenson
2023-06-24 21:15 ` Spacur [this message]
2023-06-26 19:25 ` classabbyamp
2023-06-28 21:57 ` Spacur
2023-06-28 21:57 ` [PR PATCH] [Closed]: " Spacur
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=20230624211527.kA6zyk8O3u1EDT94NmhAUIB7QM1oVjOS66NO3gQdIoE@z \
--to=spacur@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).