From: VlctM <VlctM@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Inkstitch
Date: Thu, 30 Nov 2023 20:45:51 +0100 [thread overview]
Message-ID: <20231130194551.Y52GpVN9Shbb_wLEq7CcD7QjLmLlI9ubYnvH_G1Xuc4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47503@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
New comment by VlctM on void-packages repository
https://github.com/void-linux/void-packages/pull/47503#issuecomment-1834441741
Comment:
Now I've found that rule. Somehow I missed that paragraph. Sorry. I will try to fix that problem with numpy, or I'll wait for the next release.
next prev parent reply other threads:[~2023-11-30 19:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:20 [PR PATCH] Inkstitch VlctM
2023-11-30 18:28 ` Inkstitch cinerea0
2023-11-30 19:37 ` Inkstitch VlctM
2023-11-30 19:45 ` VlctM [this message]
2023-11-30 19:45 ` [PR PATCH] [Closed]: Inkstitch VlctM
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=20231130194551.Y52GpVN9Shbb_wLEq7CcD7QjLmLlI9ubYnvH_G1Xuc4@z \
--to=vlctm@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).