From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-rust@nongnu.org
Subject: Re: [PATCH 8/9] scripts: rename get-wraps-from-cargo-registry.py
Date: Wed, 26 Aug 2026 17:11:26 +0800 [thread overview]
Message-ID: <ao6tvhi/tOx2P+e7@intel.com> (raw)
In-Reply-To: <20260821083925.2008135-9-pbonzini@redhat.com>
On Fri, Aug 21, 2026 at 10:39:23AM +0200, Paolo Bonzini wrote:
> Date: Fri, 21 Aug 2026 10:39:23 +0200
> From: Paolo Bonzini <pbonzini@redhat.com>
> Subject: [PATCH 8/9] scripts: rename get-wraps-from-cargo-registry.py
> X-Mailer: git-send-email 2.55.0
>
> It does more than that now.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> .../{get-wraps-from-cargo-registry.py => update-cargo-wraps.py} | 0
> 1 file changed, 0 insertions(+), 0 deletions(-)
> rename scripts/{get-wraps-from-cargo-registry.py => update-cargo-wraps.py} (100%)
Just a nit, these places were missed ;).
$ grep -nr get-wraps-from-cargo-registry.py
MAINTAINERS:3780:F: scripts/get-wraps-from-cargo-registry.py
scripts/update-cargo-wraps.py:6:get-wraps-from-cargo-registry.py - Update Meson subprojects from a Cargo
docs/about/build-platforms.rst:131: script, ``scripts/get-wraps-from-cargo-registry.py``, that automatically
next prev parent reply other threads:[~2026-08-26 9:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 8:39 [PATCH 0/9] scripts: introduce script to update cargo .wrap files Paolo Bonzini
2026-08-21 8:39 ` [PATCH 1/9] scripts: print build.rs diff Paolo Bonzini
2026-08-21 8:39 ` [PATCH 2/9] scripts: rename variable in scripts/get-wraps-from-cargo-registry.py Paolo Bonzini
2026-08-21 8:39 ` [PATCH 3/9] scripts: do not assume the new version of the crate is present Paolo Bonzini
2026-08-21 8:39 ` [PATCH 4/9] scripts: prepare for introduction of CrateSource class Paolo Bonzini
2026-08-21 8:39 ` [PATCH 5/9] scripts: introduce CrateSource abstract class Paolo Bonzini
2026-08-21 8:39 ` [PATCH 6/9] scripts: add functionality to update wrap files from Cargo.lock Paolo Bonzini
2026-08-21 8:39 ` [PATCH 7/9] scripts: add the possibility of a quick update of the pacakge Paolo Bonzini
2026-08-21 8:39 ` [PATCH 8/9] scripts: rename get-wraps-from-cargo-registry.py Paolo Bonzini
2026-08-26 9:11 ` Zhao Liu [this message]
2026-08-21 8:39 ` [PATCH 9/9] rust: update crates Paolo Bonzini
2026-08-24 7:17 ` [PATCH 0/9] scripts: introduce script to update cargo .wrap files Marc-André Lureau
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=ao6tvhi/tOx2P+e7@intel.com \
--to=zhao1.liu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-rust@nongnu.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 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.