From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH manager 0/4] followups for vzdump scheduling2
Date: Wed, 10 Nov 2021 21:37:04 +0100 [thread overview]
Message-ID: <137fb00e-de21-42cb-8cf8-0a4fbadae8c1@proxmox.com> (raw)
In-Reply-To: <20211110140256.1863209-1-d.csapak@proxmox.com>
On 10.11.21 15:02, Dominik Csapak wrote:
> * fixes the saving/loading of the 'prune-backups' field (oops)
> * adds correct validation for id
> * adds a comment field for jobs
>
> Dominik Csapak (4):
> Jobs/VZDump: encode/decode 'prune-backups' where needed
> ui: dc/BackupEdit: use correct validation
> api: backup/jobs: add comment field to jobs
> ui: dc/Backup: add comment field and column
>
> PVE/API2/Backup.pm | 14 ++++++++++-
> PVE/Jobs/Plugin.pm | 37 ++++++++++++++++++++++++++++++
> PVE/Jobs/VZDump.pm | 28 ++++++++++++++++++++++
> www/manager6/dc/Backup.js | 19 +++++++++++++--
> www/manager6/dc/BackupJobDetail.js | 5 ++++
> 5 files changed, 100 insertions(+), 3 deletions(-)
>
applied series for now, thanks!
prev parent reply other threads:[~2021-11-10 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 14:02 [pve-devel] " Dominik Csapak
2021-11-10 14:02 ` [pve-devel] [PATCH manager 1/4] Jobs/VZDump: encode/decode 'prune-backups' where needed Dominik Csapak
2021-11-10 14:02 ` [pve-devel] [PATCH manager 2/4] ui: dc/BackupEdit: use correct validation Dominik Csapak
2021-11-10 14:02 ` [pve-devel] [PATCH manager 3/4] api: backup/jobs: add comment field to jobs Dominik Csapak
2021-11-10 14:02 ` [pve-devel] [PATCH manager 4/4] ui: dc/Backup: add comment field and column Dominik Csapak
2021-11-10 17:18 ` [pve-devel] [PATCH manager 0/4] followups for vzdump scheduling2 Thomas Lamprecht
2021-11-10 20:37 ` 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=137fb00e-de21-42cb-8cf8-0a4fbadae8c1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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