From: Christoph Heiss <c.heiss@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH installer 0/6] small, overall install progress improvements
Date: Tue, 23 Jul 2024 12:35:10 +0200 [thread overview]
Message-ID: <zcpoczqpmh2cvnd5ypgk6kdsl67xbogzhjvi7qww7tq7dbaevb@v6dq2krnlben> (raw)
In-Reply-To: <20240516133945.1087246-1-c.heiss@proxmox.com>
Ping, still applies cleanly to current master as of today (23-07-2024).
Did a quick test round of Auto/GUI/TUI too, just to confirm everything.
On Thu, May 16, 2024 at 03:39:30PM GMT, Christoph Heiss wrote:
> 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.
>
> Christoph Heiss (6):
> test: ui2-stdio: fix multi-process testing
> 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
>
> Proxmox/Install.pm | 2 +-
> Proxmox/UI/StdIO.pm | 8 ++-
> .../src/bin/proxmox-auto-installer.rs | 35 ++++++++--
> proxmox-auto-installer/src/utils.rs | 23 -------
> proxmox-installer-common/src/setup.rs | 23 +++++++
> .../src/views/install_progress.rs | 67 +++++++------------
> test/ui2-stdio.pl | 10 +--
> 7 files changed, 88 insertions(+), 80 deletions(-)
>
> --
> 2.44.0
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
>
_______________________________________________
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-07-23 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 13:39 Christoph Heiss
2024-05-16 13:39 ` [pve-devel] [PATCH installer 1/6] test: ui2-stdio: fix multi-process testing Christoph Heiss
2024-11-10 18:50 ` [pve-devel] applied: " Thomas Lamprecht
2024-05-16 13:39 ` [pve-devel] [PATCH installer 2/6] auto, tui: move low-level installer message struct to common crate Christoph Heiss
2024-05-16 13:39 ` [pve-devel] [PATCH installer 3/6] auto: log non-json low-level messages into separate file Christoph Heiss
2024-05-16 13:39 ` [pve-devel] [PATCH installer 4/6] low-level: stdio: fix: make progress text properly optional Christoph Heiss
2024-05-16 13:39 ` [pve-devel] [PATCH installer 5/6] low-level: add proper message to 100% progress ratio update Christoph Heiss
2024-05-16 13:39 ` [pve-devel] [PATCH installer 6/6] auto: avoid printing unnecessary progress update lines Christoph Heiss
2024-07-23 10:35 ` Christoph Heiss [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=zcpoczqpmh2cvnd5ypgk6kdsl67xbogzhjvi7qww7tq7dbaevb@v6dq2krnlben \
--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 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.