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-series: [PATCH installer v2 0/6] small, overall install progress improvements
Date: Mon, 25 Nov 2024 23:25:18 +0100 [thread overview]
Message-ID: <e432448f-16e1-480f-8ea3-6422f7d63eeb@proxmox.com> (raw)
In-Reply-To: <20241125112900.988346-1-c.heiss@proxmox.com>
Am 25.11.24 um 12:27 schrieb Christoph Heiss:
> This series tries to improve upon some small things around the
> installation progress reporting, esp. in the auto-installer, as well as
> some small fixes & code-deduplication.
>
> History
> =======
>
> v1: https://lore.proxmox.com/pve-devel/20240516133945.1087246-1-c.heiss@proxmox.com/
>
> Changes v1 -> v2:
> * dropped already-applied patches
> * rebased on latest master
> * added new patch #6
>
> Diffstat
> ========
>
> Christoph Heiss (6):
> auto, tui: move low-level installer message struct to common crate
> auto: log non-json low-level messages into separate file
> low-level: stdio: fix: make progress text properly optional
> low-level: add proper message to 100% progress ratio update
> auto: avoid printing unnecessary progress update lines
> tui: tests: catch EOF from proxmox-low-level-installer early
>
> Proxmox/Install.pm | 2 +-
> Proxmox/UI/StdIO.pm | 8 +-
> .../src/bin/proxmox-auto-installer.rs | 41 ++++++++--
> proxmox-auto-installer/src/utils.rs | 23 ------
> proxmox-installer-common/src/setup.rs | 23 ++++++
> .../src/views/install_progress.rs | 76 ++++++++-----------
> test/ui2-stdio.pl | 2 +-
> 7 files changed, 98 insertions(+), 77 deletions(-)
>
applied series, thanks!
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-25 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 11:27 [pve-devel] " Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 1/6] auto, tui: move low-level installer message struct to common crate Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 2/6] auto: log non-json low-level messages into separate file Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 3/6] low-level: stdio: fix: make progress text properly optional Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 4/6] low-level: add proper message to 100% progress ratio update Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 5/6] auto: avoid printing unnecessary progress update lines Christoph Heiss
2024-11-25 11:27 ` [pve-devel] [PATCH installer v2 6/6] tui: tests: catch EOF from proxmox-low-level-installer early Christoph Heiss
2024-11-25 22:25 ` 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=e432448f-16e1-480f-8ea3-6422f7d63eeb@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.