From: Kefu Chai <k.chai@proxmox.com>
To: Wolfgang Bumiller <w.bumiller@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] applied: [PATCH proxmox-fuse-rs 0/1] Add rename operation support
Date: Tue, 23 Dec 2025 12:47:12 +0000 [thread overview]
Message-ID: <mjiku04m.5i99yzoxbmkg@proxmox.com> (raw)
In-Reply-To: <ev7hxqpat4rthlj4xbopkfcz3edqvrivb7j3vjpcmz4o7wlui2@hreq3obqqhi7>
Hi Wolfgang,
Thanks for reviewing my change.
No changes so far, this is the only change I wanted to have in proxmox-fuse-rs when porting pve-cluster to Rust.
cheers,
On Monday, 12/22/2025, 19:35, Wolfgang Bumiller <w.bumiller@proxmox.com> wrote:
applied thanks
Technically an API break so we'd have to bump to 2.0 with this. Are
there any other breaking API changes we need?
On Tue, Nov 11, 2025 at 10:37:59PM +0800, Kefu Chai wrote:
This patch implements the rename operation in proxmox-fuse-rs, which
was previously unimplemented due to lack of use cases.
The rust rewrite of pve-cluster uses proxmox-fuse-rs for its FUSE
integration and requires rename support for files exposed by plugins.
This implementation ensures feature parity with the C version of
pve-cluster.
Kefu Chai (1):
add rename operation
src/requests.rs [http://requests.rs/] | 25 +++++++++++++++++++++++++
src/session.rs [http://session.rs/] | 32 ++++++++++++++++++++++++++++++++
2 files changed, 57 insertions(+)
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-12-23 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 14:37 [pve-devel] " Kefu Chai
2025-11-11 14:38 ` [pve-devel] [PATCH proxmox-fuse-rs 1/1] add rename operation Kefu Chai
2025-12-15 6:59 ` Kefu Chai
2025-12-22 11:35 ` [pve-devel] applied: [PATCH proxmox-fuse-rs 0/1] Add rename operation support Wolfgang Bumiller
2025-12-23 12:47 ` Kefu Chai [this message]
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=mjiku04m.5i99yzoxbmkg@proxmox.com \
--to=k.chai@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/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.