From: guix-patches--- via <guix-patches@gnu.org>
To: "Efraim Flashner" <efraim@flashner.co.il>
Cc: 71914@debbugs.gnu.org
Subject: [bug#71914] [PATCH 08/10] gnu: Add rust-pyo3-macros-0.21.
Date: Wed, 03 Jul 2024 18:12:51 +0900 [thread overview]
Message-ID: <D2FSE7UQT32D.2CUN1S761AZZR@guix> (raw)
In-Reply-To: <ZoUTNw5-O74vsGfR@3900XT>
[-- Attachment #1: Type: text/plain, Size: 671 bytes --]
On 2024-07-03 at 12:00+03:00, Efraim Flashner wrote:
> On Wed, Jul 03, 2024 at 05:11:43PM +0900, Nguyễn Gia Phong wrote:
> > On 2024-07-03 at 16:57+09:00, Nguyễn Gia Phong wrote:
> > I just realized that all pyo3-* 0.20 use the same cargo-inputs
> > as 0.21. Should I send v2 for all patches or just 05 to 08?
>
> They use the 0.20 version of the inputs, not the 0.21 version of the
> inputs, so they have different cargo-inputs.
Sorry, my bad, that only applies for the 3 other pyo3-*
(I removed their arguments and rust-pyo3@0.20 built w/o any error).
Either way, what's the general etiquette for sending revisions
of a subset of the patch series?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 687 bytes --]
next prev parent reply other threads:[~2024-07-03 9:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-03 7:54 [bug#71914] [PATCH 00/10] gnu: Add python-nh3 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 01/10] gnu: rust-typed-arena-2: Update to 2.0.2 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 02/10] gnu: Add rust-markup5ever-0.12 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 03/10] gnu: Add rust-html5ever-0.27 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 04/10] gnu: Add rust-ammonia-4 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 05/10] gnu: Add rust-pyo3-build-config-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 06/10] gnu: Add rust-pyo3-ffi-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 07/10] gnu: Add rust-pyo3-macros-backend-0.21 guix-patches--- via
2024-07-03 7:57 ` [bug#71914] [PATCH 08/10] gnu: Add rust-pyo3-macros-0.21 guix-patches--- via
2024-07-03 8:11 ` guix-patches--- via
2024-07-03 9:00 ` Efraim Flashner
2024-07-03 9:12 ` guix-patches--- via [this message]
2024-07-03 9:27 ` Efraim Flashner
2024-07-03 7:58 ` [bug#71914] [PATCH 09/10] gnu: Add rust-pyo3-0.21 guix-patches--- via
2024-07-03 7:58 ` [bug#71914] [PATCH 10/10] gnu: Add python-nh3 guix-patches--- via
2024-07-03 9:07 ` bug#71914: [PATCH 00/10] " Efraim Flashner
2024-07-03 9:20 ` [bug#71914] " guix-patches--- via
2024-07-03 9:24 ` Efraim Flashner
2024-07-03 9:44 ` guix-patches--- via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D2FSE7UQT32D.2CUN1S761AZZR@guix \
--to=guix-patches@gnu.org \
--cc=71914@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=mcsinyx@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).