public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Michael Köppl" <m.koeppl@proxmox.com>
To: Christoph Heiss <c.heiss@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-installer 4/6] run rustfmt
Date: Fri, 25 Apr 2025 14:22:53 +0200	[thread overview]
Message-ID: <b96190d1-7023-4156-94ec-07d84e9dd886@proxmox.com> (raw)
In-Reply-To: <D9DZZFX6Q8HP.1MHACYAF6HFFX@proxmox.com>

On 4/23/25 13:56, Christoph Heiss wrote:
> Have you checked out the latest commit (952832147)?
> 
> These are apparently the "old" 2021 edition rules which are being
> applied here - latest master is on the 2024 edition for some time now
> [0]. The changes here are the exact reverse of some of the changes done
> in the follow-up tree-wide formatting commit [1].
> 
> (Also, running `cargo fmt` on latest master does not produce any
> changes, FWIW. So this should not be necessary - that's what caught me.)
> 
> [0] https://git.proxmox.com/?p=pve-installer.git;a=commitdiff;h=c305be5e
> [1] https://git.proxmox.com/?p=pve-installer.git;a=commitdiff;h=a1575df4
> 

Hi, thanks for having a look and for your feedback! It seems this stems 
from a configuration issue with my Neovim. For some reason the rustfmt 
used by my editor plugin did not pick up the edition = "2024" in 
rustfmt.toml. FWIW, it did work when I instead set style_edition = 
"2024", which allows explicitly setting the style used for formatting 
according to the Rust documentation [0]. I suppose it's more of a 
configuration error on my side, though. I checked again to ensure the 
other patches are not affected. I suppose this one could just be 
omitted? Or should I send a new series?

[0] 
https://doc.rust-lang.org/edition-guide/rust-2024/rustfmt-style-edition.html


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2025-04-25 12:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 16:27 [pve-devel] [PATCH installer 0/6] add early disk and network sanity checks Michael Köppl
2025-04-22 16:27 ` [pve-devel] [PATCH pve-installer 1/6] auto: add early answer file sanity check for RAID configurations Michael Köppl
2025-04-28 11:25   ` Christoph Heiss
2025-04-28 14:31     ` Michael Köppl
2025-04-29  8:26       ` Christoph Heiss
2025-04-29  9:32         ` Michael Köppl
2025-04-29  9:40           ` Christoph Heiss
2025-04-22 16:27 ` [pve-devel] [PATCH pve-installer 2/6] common: use get_min_disks as single source of truth for RAID config checks Michael Köppl
2025-04-28 11:48   ` Christoph Heiss
2025-04-28 15:36     ` Michael Köppl
2025-04-22 16:27 ` [pve-devel] [RFC PATCH pve-installer 3/6] close #5887: add sanity check for LVM swapsize and maxroot Michael Köppl
2025-04-28 12:00   ` Christoph Heiss
2025-04-29 11:30     ` Michael Köppl
2025-04-22 16:27 ` [pve-devel] [PATCH pve-installer 4/6] run rustfmt Michael Köppl
2025-04-23 11:56   ` Christoph Heiss
2025-04-25 12:22     ` Michael Köppl [this message]
2025-04-22 16:27 ` [pve-devel] [PATCH pve-installer 5/6] common: add more descriptive errors for invalid network configs Michael Köppl
2025-04-28 12:20   ` Christoph Heiss
2025-04-22 16:27 ` [pve-devel] [RFC PATCH pve-installer 6/6] closes #5757: common: add checks for valid IPv4 address within subnet Michael Köppl
2025-04-28 10:22   ` Christoph Heiss
2025-04-28 14:20     ` Michael Köppl
2025-04-28 12:25 ` [pve-devel] [PATCH installer 0/6] add early disk and network sanity checks Christoph Heiss
2025-04-29 14:14   ` Michael Köppl

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=b96190d1-7023-4156-94ec-07d84e9dd886@proxmox.com \
    --to=m.koeppl@proxmox.com \
    --cc=c.heiss@proxmox.com \
    --cc=pve-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal