From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Hannes Laimer <h.laimer@proxmox.com>
Subject: [pbs-devel] applied-series: [PATCH proxmox-backup 0/2] local sync follow-up
Date: Mon, 27 Nov 2023 14:50:39 +0100 [thread overview]
Message-ID: <0e6331c8-d0e2-4ba4-8e32-e2bb990acae8@proxmox.com> (raw)
In-Reply-To: <20231127115944.209681-1-h.laimer@proxmox.com>
On 27.11.23 12:59, Hannes Laimer wrote:
> two small follow-ups for local sync
>
> Hannes Laimer (2):
> ui: fix sync job initial loading of local datastores
> config: don't allow creation of sync job to same datastore
>
> src/api2/config/sync.rs | 4 ++++
> www/window/SyncJobEdit.js | 1 +
> 2 files changed, 5 insertions(+)
>
applied series, thanks!
prev parent reply other threads:[~2023-11-27 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 11:59 [pbs-devel] " Hannes Laimer
2023-11-27 11:59 ` [pbs-devel] [PATCH proxmox-backup 1/2] ui: fix sync job initial loading of local datastores Hannes Laimer
2023-11-27 11:59 ` [pbs-devel] [PATCH proxmox-backup 2/2] config: don't allow creation of sync job to same datastore Hannes Laimer
2023-11-27 13:50 ` 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=0e6331c8-d0e2-4ba4-8e32-e2bb990acae8@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=h.laimer@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