From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 6855A1FF140 for ; Fri, 24 Apr 2026 21:10:44 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 750F41EFE1; Fri, 24 Apr 2026 21:10:39 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH proxmox-backup 0/3] followups s3 datastores Date: Fri, 24 Apr 2026 21:06:48 +0200 Message-ID: <177705760889.3360887.10647576519185054377.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260424125027.804185-1-c.ebner@proxmox.com> References: <20260424125027.804185-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777057742492 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.002 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: CRYX2QV54HXIQBUMSWAEZUBRWX5WJMNI X-Message-ID-Hash: CRYX2QV54HXIQBUMSWAEZUBRWX5WJMNI X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: 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