public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Daniel Tschlatscher <d.tschlatscher@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-qemu v2] fix: 3865: backup restore human readable output
Date: Fri, 25 Mar 2022 09:51:52 +0100	[thread overview]
Message-ID: <04f521d1-7cc0-f47e-bdd8-b0346904ffa9@proxmox.com> (raw)
In-Reply-To: <20220325083437.498400-1-d.tschlatscher@proxmox.com>

On 25.03.22 09:34, Daniel Tschlatscher wrote:
> The backup restore dialogue now displays size information and duration in a format more easily understandable for humans. The output was adapated to match the output of the backup create dialogue where possible.
> Added 2 helper methods for displaying bytes and time in human readable format.
> 
> Signed-off-by: Daniel Tschlatscher <d.tschlatscher@proxmox.com>
> ---
> 
> Changes to v1: Fixed the indentation (there were a few rogue tab stops) and fixed a typo in the commit message

for such changes I'd wait out for an actual review to avoid noise, e.g.,
like I made on 5 minutes ago ;-P

Also, this depends on the type of work, but for new functionality in repos
where we use debian/patches for applying downstream work it can be worth
to send out the (initial) revisions as "inner" patch, i.e., like they'd come
directly from the upstream patched repo, that makes review easier.

A patch-patch can then be either sent once all is ready and reviewed OK, or
also done by the applier (depends on the appliers' preferences, I often don't
mind doing so)




      reply	other threads:[~2022-03-25  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-25  8:34 Daniel Tschlatscher
2022-03-25  8:51 ` 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=04f521d1-7cc0-f47e-bdd8-b0346904ffa9@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.tschlatscher@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