From: fanyx <fanyx@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: freerdp3-3.5.0
Date: Sat, 20 Apr 2024 16:42:50 +0200 [thread overview]
Message-ID: <20240420144250.A5B9223D63@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49572@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 243 bytes --]
New comment by fanyx on void-packages repository
https://github.com/void-linux/void-packages/pull/49572#issuecomment-2067694981
Comment:
https://packages.debian.org/sid/libuwac0-dev
sounds reasonable to extract libuwac to its own package
next prev parent reply other threads:[~2024-04-20 14:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 19:17 [PR PATCH] freerdp: update to 3.4.0 fanyx
2024-03-28 13:04 ` [PR PATCH] [Updated] " fanyx
2024-03-28 13:22 ` fanyx
2024-03-28 14:29 ` fanyx
2024-03-28 14:38 ` fanyx
2024-03-28 15:06 ` chrysos349
2024-03-28 15:49 ` fanyx
2024-03-28 16:08 ` [PR PATCH] [Updated] " fanyx
2024-03-28 16:10 ` [PR PATCH] [Updated] New package: freerdp3-3.4.0 fanyx
2024-03-28 23:37 ` fanyx
2024-03-28 23:50 ` fanyx
2024-03-28 23:56 ` fanyx
2024-04-20 13:38 ` [PR PATCH] [Updated] " fanyx
2024-04-20 14:42 ` fanyx [this message]
2024-04-20 16:49 ` New package: freerdp3-3.5.0 fanyx
2024-04-21 10:45 ` [PR PATCH] [Updated] " fanyx
2024-04-22 10:29 ` fanyx
2024-04-22 10:31 ` fanyx
2024-04-22 10:41 ` [PR PATCH] [Updated] freerdp split (2.11.5, 3.5.0, libuwac0) fanyx
2024-04-22 10:56 ` fanyx
2024-04-22 12:01 ` chrysos349
2024-04-22 12:03 ` [PR PATCH] [Closed]: " fanyx
2024-04-22 12:03 ` fanyx
2024-04-22 11:33 [PR PATCH] New package: freerdp3-3.5.0 chrysos349
2024-04-22 12:20 ` ahesford
2024-04-22 12:41 ` fanyx
2024-04-22 12:42 ` fanyx
2024-04-22 13:10 ` chrysos349
2024-04-22 13:20 ` chrysos349
2024-04-22 14:46 ` ahesford
2024-04-22 14:47 ` ahesford
2024-04-22 15:58 ` chrysos349
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=20240420144250.A5B9223D63@inbox.vuxu.org \
--to=fanyx@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).