From: Hanuko33 <Hanuko33@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: SDL3-3.2.0
Date: Sun, 26 Jan 2025 20:04:07 +0100 [thread overview]
Message-ID: <20250126190407.992CD21F10@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54106@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
New comment by Hanuko33 on void-packages repository
https://github.com/void-linux/void-packages/pull/54106#issuecomment-2614550552
Comment:
I tested the changes more on my machine.
Everything seems fine to me.
Also, the package requirements are with a question mark, because I really don't know if SDL3 will succeed (and be useful).
I checked on the archlinux repo, and it seems to have a bit of programs already written in it.
next prev parent reply other threads:[~2025-01-26 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 15:48 [PR PATCH] " Hanuko33
2025-01-26 19:04 ` Hanuko33 [this message]
2025-02-03 7:13 ` [PR PATCH] [Merged]: " Gottox
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=20250126190407.992CD21F10@inbox.vuxu.org \
--to=hanuko33@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).