From: PaperMountainStudio <PaperMountainStudio@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: streamlink: update to 1.6.0
Date: Sat, 03 Oct 2020 16:37:29 +0200 [thread overview]
Message-ID: <20201003143729.RtTHLKrDvMUS5zVUbhSMUlBBZpPnZKpvoKk2YapxFxc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25227@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 221 bytes --]
New comment by PaperMountainStudio on void-packages repository
https://github.com/void-linux/void-packages/pull/25227#issuecomment-703113657
Comment:
oops, I didn't catch this. It should be fine now. Thanks @Chocimier
next prev parent reply other threads:[~2020-10-03 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 11:52 [PR PATCH] " PaperMountainStudio
2020-10-02 17:38 ` Chocimier
2020-10-02 18:35 ` [PR PATCH] [Updated] " PaperMountainStudio
2020-10-03 14:37 ` PaperMountainStudio [this message]
2020-10-03 15:56 ` [PR PATCH] [Merged]: " Chocimier
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=20201003143729.RtTHLKrDvMUS5zVUbhSMUlBBZpPnZKpvoKk2YapxFxc@z \
--to=papermountainstudio@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).