From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH proxmox-backup 0/3] followups s3 datastores
Date: Fri, 24 Apr 2026 21:06:48 +0200 [thread overview]
Message-ID: <177705760889.3360887.10647576519185054377.b4-ty@b4> (raw)
In-Reply-To: <20260424125027.804185-1-c.ebner@proxmox.com>
On Fri, 24 Apr 2026 14:50:23 +0200, Christian Ebner wrote:
> These patches are some followups for the s3 datastores, which are
> moving from tech preview to be fully supported. Therefore extend
> on still missing documentation and drop a still present tech preview
> label in the datastore create dialog.
>
> Christian Ebner (3):
> docs: describe s3 request notifications and threshold reset schedule
> docs: mention still missing field in the configuration subtree
> ui: drop 'tech preview' label for s3 stores in creation dialog
>
> [...]
Applied, thanks!
[1/3] docs: describe s3 request notifications and threshold reset schedule
commit: 304f6d19251f8be33ef784386617002e939b7557
[2/3] docs: mention still missing field in the configuration subtree
commit: dedf4e83fab2f9a9c7a73510124921e93f3c178a
[3/3] ui: drop 'tech preview' label for s3 stores in creation dialog
commit: ecd8e0dff2b46ddb37ce62702c6f5b8528eedf97
prev parent reply other threads:[~2026-04-24 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 12:50 Christian Ebner
2026-04-24 12:50 ` [PATCH proxmox-backup 1/3] docs: describe s3 request notifications and threshold reset schedule Christian Ebner
2026-04-24 12:50 ` [PATCH proxmox-backup 2/3] docs: mention still missing field in the configuration subtree Christian Ebner
2026-04-24 12:50 ` [PATCH proxmox-backup 3/3] ui: drop 'tech preview' label for s3 stores in creation dialog Christian Ebner
2026-04-24 19:06 ` 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=177705760889.3360887.10647576519185054377.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=c.ebner@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