From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Stefan Lendl <s.lendl@proxmox.com>
Subject: [pbs-devel] applied: [PATCH v2 proxmox-backup 1/1] PruneJobEdit disallow blank schedule value
Date: Mon, 25 Mar 2024 18:03:34 +0100 [thread overview]
Message-ID: <45e674e7-da5a-4dc2-80f1-260ca2d51e6c@proxmox.com> (raw)
In-Reply-To: <20240307133342.198417-2-s.lendl@proxmox.com>
Am 07/03/2024 um 14:33 schrieb Stefan Lendl:
> The schedule value for prune jobs can not be empty.
>
> Signed-off-by: Stefan Lendl <s.lendl@proxmox.com>
> ---
>
> Changes v1 -> v2:
> * minimal whitespace fix to make it apply
>
> www/window/PruneJobEdit.js | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
>
applied, with slight rewording of the commit subject, thanks!
prev parent reply other threads:[~2024-03-25 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 13:33 [pbs-devel] " Stefan Lendl
2024-03-07 13:39 ` Gabriel Goller
2024-03-07 13:50 ` Stefan Lendl
2024-03-07 13:53 ` Gabriel Goller
2024-03-25 17:03 ` 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=45e674e7-da5a-4dc2-80f1-260ca2d51e6c@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.lendl@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