all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: <71914@debbugs.gnu.org>
Subject: [bug#71914] [PATCH 08/10] gnu: Add rust-pyo3-macros-0.21.
Date: Wed, 03 Jul 2024 17:11:43 +0900	[thread overview]
Message-ID: <D2FR3EP2Z5K1.1SEIS496OLSCS@guix> (raw)
In-Reply-To: <8f5311fba8e591543e7d8e544555b2efceb4bc92.1719992277.git.mcsinyx@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 665 bytes --]

On 2024-07-03 at 16:57+09:00, Nguyễn Gia Phong wrote:
> * gnu/packages/crates-io.scm (rust-pyo3-macros-0.20):
> Inherit from rust-pyo3-macros-0.21.
> Update to 0.20.3.
> ---
> +(define-public rust-pyo3-macros-0.20
> +  (package
> +    (inherit rust-pyo3-macros-0.21)
[snip]
> +    (arguments
> +     `(#:cargo-inputs
> +       (("rust-proc-macro2" ,rust-proc-macro2-1)
> +        ("rust-pyo3-macros-backend" ,rust-pyo3-macros-backend-0.20)
> +        ("rust-quote" ,rust-quote-1)
> +        ("rust-syn" ,rust-syn-2))))))

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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 687 bytes --]

  reply	other threads:[~2024-07-03  8:12 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 [this message]
2024-07-03  9:00     ` Efraim Flashner
2024-07-03  9:12       ` guix-patches--- via
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D2FR3EP2Z5K1.1SEIS496OLSCS@guix \
    --to=guix-patches@gnu.org \
    --cc=71914@debbugs.gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.