From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [pve-devel] [RFC PATCH v2 proxmox-backup-qemu] restore: make chunk loading more parallel
Date: Tue, 8 Jul 2025 11:03:22 +0200 [thread overview]
Message-ID: <fca5df96-37ab-4d21-a8d0-edac04e319d0@proxmox.com> (raw)
In-Reply-To: <362c4660-cef7-4e77-b9ac-50fd94e3caf3@proxmox.com>
Am 08.07.25 um 10:52 schrieb Dominik Csapak:
> Sorry, i sent the patch to the wrong list, this was originally meant for
> pve-devel instead. Should i resend it there?
You can do both as this is relevant for both projects and lists
can be accumulative, not just either/or.
_______________________________________________
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-07-08 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 8:49 [pbs-devel] " Dominik Csapak
2025-07-08 8:52 ` Dominik Csapak
2025-07-08 9:03 ` Thomas Lamprecht [this message]
[not found] ` <9dc2c099169ee1ed64c274d64cc0a1c19f9f6c92.camel@notnullmakers.com>
2025-07-08 10:58 ` Dominik Csapak
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=fca5df96-37ab-4d21-a8d0-edac04e319d0@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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