From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: devilutionX: update to 1.4.1.
Date: Sun, 15 Jan 2023 17:14:11 +0100 [thread overview]
Message-ID: <20230115161411.Brt5yWZElI0iBVPQREpD9-ZqB5ZH9BYSYsocqWv3jTc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41658@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
New comment by kruceter on void-packages repository
https://github.com/void-linux/void-packages/pull/41658#issuecomment-1383190462
Comment:
> Is there a source for `smpq` upstream?
There is, but my main concern is that its last release was in 2016, last change to the code in 2018. If it is alright, I will package it for you properly.
next prev parent reply other threads:[~2023-01-15 16:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 1:39 [PR PATCH] " kruceter
2023-01-15 2:54 ` [PR PATCH] [Updated] " kruceter
2023-01-15 3:09 ` kruceter
2023-01-15 3:22 ` kruceter
2023-01-15 16:00 ` [PR REVIEW] " Vaelatern
2023-01-15 16:00 ` Vaelatern
2023-01-15 16:00 ` Vaelatern
2023-01-15 16:00 ` Vaelatern
2023-01-15 16:00 ` Vaelatern
2023-01-15 16:01 ` Vaelatern
2023-01-15 16:05 ` [PR REVIEW] " kruceter
2023-01-15 16:06 ` kruceter
2023-01-15 16:12 ` kruceter
2023-01-15 16:13 ` kruceter
2023-01-15 16:14 ` kruceter [this message]
2023-01-15 16:18 ` kruceter
2023-01-15 16:32 ` Vaelatern
2023-01-15 16:33 ` [PR REVIEW] " Vaelatern
2023-01-15 18:04 ` [PR PATCH] [Updated] " kruceter
2023-01-15 18:08 ` kruceter
2023-01-15 18:46 ` [PR PATCH] [Merged]: " Vaelatern
-- strict thread matches above, loose matches on Subject: below --
2022-09-09 13:47 [PR PATCH] " chloris-pale-green
2022-09-09 14:04 ` chloris-pale-green
2022-09-10 6:10 ` tranzystorek-io
2022-09-10 6:12 ` tranzystorek-io
2022-09-10 12:25 ` chloris-pale-green
2022-12-10 1:58 ` github-actions
2022-12-22 15:44 ` bugcrazy
2022-12-23 2:29 ` bugcrazy
2023-01-11 18:45 ` kruceter
2023-01-12 7:49 ` chloris-pale-green
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=20230115161411.Brt5yWZElI0iBVPQREpD9-ZqB5ZH9BYSYsocqWv3jTc@z \
--to=kruceter@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).