From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: makemkv-1.17.2
Date: Thu, 03 Aug 2023 20:46:16 +0200 [thread overview]
Message-ID: <20230803184616.m-xW0f9XcIQNyyjRf_I3nGO0I31JBDe9lWGVBUkYc50@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27960@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 288 bytes --]
New comment by Chocimier on void-packages repository
https://github.com/void-linux/void-packages/pull/27960#issuecomment-1664464645
Comment:
> It's being shipped by a few other distros as well
Almost all or them don't host packages but instruct package manager to fetch from origin.
next prev parent reply other threads:[~2023-08-03 18:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 23:42 [PR PATCH] New package: makemkv-1.15.4 jcgruenhage
2021-01-15 23:59 ` [PR PATCH] [Updated] " jcgruenhage
2021-01-18 17:44 ` Chocimier
2021-01-19 0:16 ` jcgruenhage
2021-01-19 13:16 ` [PR PATCH] [Updated] " jcgruenhage
2021-06-21 10:09 ` [PR REVIEW] " jcgruenhage
2022-05-02 2:16 ` github-actions
2022-05-03 9:06 ` [PR PATCH] [Updated] " jcgruenhage
2022-05-03 9:07 ` jcgruenhage
2022-05-03 9:20 ` jcgruenhage
2022-05-07 21:59 ` Piraty
2022-05-07 22:07 ` Chocimier
2022-08-07 2:13 ` github-actions
2022-08-07 7:39 ` jcgruenhage
2022-08-07 7:40 ` [PR PATCH] [Updated] " jcgruenhage
2022-08-07 10:51 ` New package: makemkv-1.17.1 jcgruenhage
2022-11-07 2:12 ` github-actions
2022-11-14 9:37 ` [PR PATCH] [Updated] " jcgruenhage
2022-11-14 9:37 ` jcgruenhage
2023-01-22 1:46 ` New package: makemkv-1.17.2 agausmann
2023-01-27 1:01 ` agausmann
2023-04-27 1:52 ` github-actions
2023-05-03 18:46 ` jcgruenhage
2023-08-03 1:48 ` github-actions
2023-08-03 18:39 ` Chocimier
2023-08-03 18:46 ` Chocimier [this message]
2023-11-03 1:45 ` github-actions
2023-11-17 1:46 ` [PR PATCH] [Closed]: " github-actions
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=20230803184616.m-xW0f9XcIQNyyjRf_I3nGO0I31JBDe9lWGVBUkYc50@z \
--to=chocimier@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).