From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Mira Limbeck <m.limbeck@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] applied: [PATCH v2 proxmox-backup 2/2] add versions command to proxmox-backup-manager
Date: Thu, 12 Nov 2020 10:29:49 +0100 [thread overview]
Message-ID: <72ee447c-6b14-044c-3e6d-e779ca2d90ba@proxmox.com> (raw)
In-Reply-To: <c16a8594-0f66-eadb-1063-d6309187a4e5@proxmox.com>
FYI: Including the mailing list again in CC.
On 12.11.20 10:11, Mira Limbeck wrote:
> So we print proxmox-backup with the kernel version instead of proxmox-backup-server in the non-verbose case?
no, the slice should be selecting the second package, fixed.
>
> This is at least different from pveversion as that prints pve-manager and not proxmox-ve.
>
> And with this change the output-format also changes the amount of information (json and json-pretty -> full output, text (default) -> only a subset)
yes, that's intended and what an user interface, be it CLI or web, is for.
Just dumping the whole state does not makes sense here for the user, same
as the web interface shouldn't just dump the raw state it gets from an
API response, different presentation require selecting different data shown
to point at the thing one actually want to present to the user.
If we just could always dump the whole state we could just auto generate
the whole user interfaces, but those tend to be pretty confusing and unusable
for most.
next prev parent reply other threads:[~2020-11-12 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 13:22 [pbs-devel] [PATCH v2 proxmox-backup 1/2] add extra_info field to APTUpdateInfo Mira Limbeck
2020-11-10 13:22 ` [pbs-devel] [PATCH v2 proxmox-backup 2/2] add versions command to proxmox-backup-manager Mira Limbeck
2020-11-11 17:38 ` [pbs-devel] applied: " Thomas Lamprecht
2020-11-12 9:12 ` [pbs-devel] [PATCH proxmox-backup] apt: use typed response for get_versions Stefan Reiter
2020-11-12 9:18 ` [pbs-devel] applied: " Thomas Lamprecht
[not found] ` <c16a8594-0f66-eadb-1063-d6309187a4e5@proxmox.com>
2020-11-12 9:29 ` Thomas Lamprecht [this message]
2020-11-11 11:59 ` [pbs-devel] [PATCH v2 proxmox-backup 1/2] add extra_info field to APTUpdateInfo Mira Limbeck
2020-11-11 17:33 ` [pbs-devel] applied: " 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=72ee447c-6b14-044c-3e6d-e779ca2d90ba@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=m.limbeck@proxmox.com \
--cc=pbs-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