From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com, Robert Obkircher <r.obkircher@proxmox.com>
Subject: applied: [PATCH v2 proxmox-backup 0/3] improve handling of bad S3 chunks during GC
Date: Thu, 23 Jul 2026 21:13:42 +0200 [thread overview]
Message-ID: <178483401003.1907934.2770482722210575737.b4-ty@b4> (raw)
In-Reply-To: <20260723095440.83690-1-r.obkircher@proxmox.com>
On Thu, 23 Jul 2026 11:54:08 +0200, Robert Obkircher wrote:
> Changes since [v1]:
> * restricted visibility of new functions to pub(crate)
>
> [v1] https://lore.proxmox.com/pbs-devel/20260713132338.170565-1-r.obkircher@proxmox.com/
>
> Robert Obkircher (3):
> datastore: fix local path for .i.bad chunk files during S3 GC
> datastore: check that .i.bad files from S3 actually match that pattern
> datastore: introduce helper function to parse digest from S3ObjectKey
>
> [...]
Applied, thanks!
[1/3] datastore: fix local path for .i.bad chunk files during S3 GC
commit: 1de3ede593ae292e75c37a8ab272bd73e2c1953b
[2/3] datastore: check that .i.bad files from S3 actually match that pattern
commit: 5f87c33eee868401ae679bb940719b91431469e3
[3/3] datastore: introduce helper function to parse digest from S3ObjectKey
commit: ca72e203c349aae9289186a395d99360873ab56f
prev parent reply other threads:[~2026-07-23 19:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 9:54 [PATCH v2 proxmox-backup 0/3] improve handling of bad S3 chunks during GC Robert Obkircher
2026-07-23 9:54 ` [PATCH v2 proxmox-backup 1/3] datastore: fix local path for .i.bad chunk files during S3 GC Robert Obkircher
2026-07-23 9:54 ` [PATCH v2 proxmox-backup 2/3] datastore: check that .i.bad files from S3 actually match that pattern Robert Obkircher
2026-07-23 9:54 ` [PATCH v2 proxmox-backup 3/3] datastore: introduce helper function to parse digest from S3ObjectKey Robert Obkircher
2026-07-23 19:13 ` 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=178483401003.1907934.2770482722210575737.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=r.obkircher@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