From: r-ricci <r-ricci@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mpg123: update to 1.30.0.
Date: Thu, 30 Jun 2022 20:00:36 +0200 [thread overview]
Message-ID: <20220630180036.ybzFcmbFxV8olHyqqwY9UhL2HotR-vTSY1f63a0TZ0g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37754@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
New comment by r-ricci on void-packages repository
https://github.com/void-linux/void-packages/pull/37754#issuecomment-1171519206
Comment:
> nobody complained about it
Before this release there was only the non-TLS internal implementation.
Anyway, I think leaving the dependency out is fine.
next prev parent reply other threads:[~2022-06-30 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 10:02 [PR PATCH] " r-ricci
2022-06-30 15:08 ` Duncaen
2022-06-30 18:00 ` r-ricci [this message]
2022-06-30 18:03 ` [PR PATCH] [Updated] " r-ricci
2022-07-01 5:34 ` [PR PATCH] [Merged]: " 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=20220630180036.ybzFcmbFxV8olHyqqwY9UhL2HotR-vTSY1f63a0TZ0g@z \
--to=r-ricci@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).