From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com,
Christian Ebner <c.ebner@proxmox.com>
Subject: [pve-devel] applied: [pbs-devel] [PATCH] docs: rephrase and extend rate limiting description for sync jobs
Date: Wed, 16 Jul 2025 00:17:50 +0200 [thread overview]
Message-ID: <175261786566.2452839.5494953215753705039.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250623124543.590388-1-c.ebner@proxmox.com>
On Mon, 23 Jun 2025 14:45:43 +0200, Christian Ebner wrote:
> Since commit 37a85cf6 ("fix: ui: sync job: edit rate limit based on
> sync direction") rate limits for sync jobs can be correctly applied
> for both directions. State this in the documentation and explicitley
> mention the directions to reduce confusion.
>
> Further, also mention the burst parameters, as they are not mentioned
> at all.
>
> [...]
Applied to master and stable-3, thanks!
[1/1] docs: rephrase and extend rate limiting description for sync jobs
commit: 4cba26673d72446bcc008e0aedc4eb7ca3fdac14
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
parent reply other threads:[~2025-07-15 22:18 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250623124543.590388-1-c.ebner@proxmox.com>]
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=175261786566.2452839.5494953215753705039.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pbs-devel@lists.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