From: Christoph Heiss <c.heiss@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH installer 0/2] fix rustdoc warnings
Date: Tue, 3 Dec 2024 11:15:16 +0100 [thread overview]
Message-ID: <20241203101542.261333-1-c.heiss@proxmox.com> (raw)
Pretty trivial overall, just re-formats some comments in accordance with
rustdoc - mostly URLs, which need to be surrounded by < > to be properly
recognised/parsed.
Christoph Heiss (2):
tree-wide: fix `cargo doc` warnings
tree-wide: run `cargo fmt`
proxmox-auto-install-assistant/src/main.rs | 10 +++++----
proxmox-installer-common/src/options.rs | 21 +++++++++++++------
proxmox-installer-common/src/utils.rs | 23 ++++++++++++++-------
proxmox-post-hook/src/main.rs | 8 +++----
proxmox-tui-installer/src/views/bootdisk.rs | 2 +-
5 files changed, 41 insertions(+), 23 deletions(-)
--
2.47.0
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2024-12-03 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 10:15 Christoph Heiss [this message]
2024-12-03 10:15 ` [pve-devel] [PATCH installer 1/2] tree-wide: " Christoph Heiss
2024-12-03 10:15 ` [pve-devel] [PATCH installer 2/2] tree-wide: run `cargo fmt` Christoph Heiss
2024-12-03 17:16 ` [pve-devel] applied-series: [PATCH installer 0/2] fix rustdoc warnings Thomas Lamprecht
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=20241203101542.261333-1-c.heiss@proxmox.com \
--to=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