From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] api: chunk reader: make reading from filesystem fully async
Date: Thu, 27 Nov 2025 10:03:25 +0100 [thread overview]
Message-ID: <d5b3bf75-d7c6-40a5-a71d-b0638fb5feb5@proxmox.com> (raw)
In-Reply-To: <fa1dafde-3dc6-44b0-a6cc-b161f3ff1b30@proxmox.com>
Am 27.11.25 um 09:54 schrieb Christian Ebner:
> True, fully async is indeed overreaching and incorrect.
>
> Can send a v2 with the commit message adapted if requested. Just to clarify
as this came up in off-list discussion with Fabian. I do not expect this to be
the cause of the issues as reported by the users, so finding that has priority.
Yeah, no worries, this is just a nit.
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-11-27 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 16:28 Christian Ebner
2025-11-26 18:10 ` Thomas Lamprecht
2025-11-27 8:55 ` Christian Ebner
2025-11-27 9:03 ` Thomas Lamprecht [this message]
2025-11-27 9:01 ` Fabian Grünbichler
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=d5b3bf75-d7c6-40a5-a71d-b0638fb5feb5@proxmox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.