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: [pbs-devel] applied: [PATCH proxmox-backup 0/2] docs: extend S3 related documentation
Date: Wed, 23 Jul 2025 13:51:31 +0200 [thread overview]
Message-ID: <175327148852.3477787.158036020565301209.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250723080231.189207-1-c.ebner@proxmox.com>
On Wed, 23 Jul 2025 10:02:29 +0200, Christian Ebner wrote:
> Two additional patches to improve the documentation for the S3 backend.
>
> The first adds a warning for the costs which might arise from operating
> the S3 backed datastore, the second shows some concrete, provider
> specific configuration examples.
>
> Christian Ebner (2):
> docs: s3: add warning of potential costs when using s3 backends
> docs: s3: add object store provider specific configuration examples
>
> [...]
Applied, thanks!
[1/2] docs: s3: add warning of potential costs when using s3 backends
(no commit info)
[2/2] docs: s3: add object store provider specific configuration examples
(no commit info)
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
prev parent reply other threads:[~2025-07-23 11:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 8:02 [pbs-devel] " Christian Ebner
2025-07-23 8:02 ` [pbs-devel] [PATCH proxmox-backup 1/2] docs: s3: add warning of potential costs when using s3 backends Christian Ebner
2025-07-23 8:02 ` [pbs-devel] [PATCH proxmox-backup 2/2] docs: s3: add object store provider specific configuration examples Christian Ebner
2025-07-23 11:45 ` [pbs-devel] [PATCH proxmox-backup 0/2] docs: extend S3 related documentation Lukas Wagner
2025-07-23 11:51 ` 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=175327148852.3477787.158036020565301209.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