From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Some cython updates on top of #45086
Date: Fri, 21 Jul 2023 03:42:19 +0200 [thread overview]
Message-ID: <20230721014219.yFqe8-h14wsnGqpBULngfYqhCrnCVYHdFp3IwurlT6g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45161@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/45161#issuecomment-1644872511
Comment:
Sigh, thanks for catching the pybind11 incompatibility. I fixed this on master already and incorporated all of your commits to date in my cython PR. You can close this PR, or you can leave it open and add any later commits after rebasing on my current branch. (You can also PR against the cython branch on my void-packages fork and I'll pull your changes there.)
next prev parent reply other threads:[~2023-07-21 1:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 22:56 [PR PATCH] " tornaria
2023-07-20 23:11 ` tornaria
2023-07-20 23:49 ` [PR PATCH] [Updated] " tornaria
2023-07-20 23:50 ` tornaria
2023-07-21 1:42 ` ahesford [this message]
2023-07-21 19:53 ` [PR PATCH] [Closed]: " tornaria
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=20230721014219.yFqe8-h14wsnGqpBULngfYqhCrnCVYHdFp3IwurlT6g@z \
--to=ahesford@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).