From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: [pve-devel] applied: [PATCH installer 0/2] rustfmt & clippy warning fix
Date: Fri, 3 Nov 2023 12:53:17 +0100 [thread overview]
Message-ID: <5abc4cbc-8ab2-433d-8af3-f080de34e797@proxmox.com> (raw)
In-Reply-To: <20231103095016.286953-1-c.heiss@proxmox.com>
On 03/11/2023 10:49, Christoph Heiss wrote:
> First patch is just a mechanical rustfmt, which I apparently missed to
> check during review - that's on me. Second patch fixes a longer-standing
> clippy warning.
>
> Christoph Heiss (2):
> tui, common: run rustfmt
> tui: fix clippy warning
>
> proxmox-installer-common/src/setup.rs | 1 -
> proxmox-tui-installer/src/main.rs | 2 +-
> proxmox-tui-installer/src/options.rs | 12 ++++++------
> proxmox-tui-installer/src/setup.rs | 14 +++++---------
> proxmox-tui-installer/src/views/bootdisk.rs | 10 ++++++----
> proxmox-tui-installer/src/views/timezone.rs | 4 +---
> proxmox-tui-installer/rustfmt.toml => rustfmt.toml | 0
> 7 files changed, 19 insertions(+), 24 deletions(-)
> rename proxmox-tui-installer/rustfmt.toml => rustfmt.toml (100%)
>
> --
> 2.42.0
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
applied, thanks!
prev parent reply other threads:[~2023-11-03 11:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 9:49 [pve-devel] " Christoph Heiss
2023-11-03 9:49 ` [pve-devel] [PATCH installer 1/2] tui, common: run rustfmt Christoph Heiss
2023-11-03 9:49 ` [pve-devel] [PATCH installer 2/2] tui: fix clippy warning Christoph Heiss
2023-11-03 11:53 ` Thomas Lamprecht [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=5abc4cbc-8ab2-433d-8af3-f080de34e797@proxmox.com \
--to=t.lamprecht@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 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.