From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pbs-devel@lists.proxmox.com,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: applied: [PATCH proxmox-backup] snapshot locking: improve error contexts
Date: Wed, 28 Oct 2026 20:48:52 +0100 [thread overview]
Message-ID: <179321686586.2278586.1099123239461455991.b4-ty@b4> (raw)
In-Reply-To: <20261023121152.760779-1-f.gruenbichler@proxmox.com>
On Fri, 23 Oct 2026 14:11:29 +0200, Fabian Grünbichler wrote:
> having the struct-debug representation logged is rather noisy, the relative
> path contains all the relevant information.
Applied, thanks!
[1/1] snapshot locking: improve error contexts
commit: cc9e1bef354ebfd21e680f138e8ce7f7d2e87185
prev parent reply other threads:[~2026-10-28 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 12:11 [PATCH proxmox-backup] snapshot locking: improve error contexts Fabian Grünbichler
2026-10-28 19:48 ` 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=179321686586.2278586.1099123239461455991.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@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