From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [pve-devel] [PATCH proxmox-backup/common/storage/wt v2] add tar.zst download in pve
Date: Thu, 19 Oct 2023 09:20:01 +0200 [thread overview]
Message-ID: <5a2d3c7e-1b49-4534-93c6-e61b1aef20bc@proxmox.com> (raw)
In-Reply-To: <20220713094317.2423116-1-d.csapak@proxmox.com>
ping (sorry i waited for such a long time ;) )
it probably does not apply anymore, but i'd like to get feedback
before starting the rebase
prev parent reply other threads:[~2023-10-19 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 9:43 [pbs-devel] " Dominik Csapak
2022-07-13 9:43 ` [pbs-devel] [PATCH proxmox-backup v2 1/4] file-restore: update dependencies Dominik Csapak
2022-10-05 16:51 ` Thomas Lamprecht
2022-10-05 16:53 ` Thomas Lamprecht
2022-07-13 9:43 ` [pbs-devel] [PATCH proxmox-backup v2 2/4] pbs-api-types: add FileRestoreFormat type Dominik Csapak
2022-10-05 16:51 ` [pbs-devel] applied: " Thomas Lamprecht
2022-10-05 16:52 ` Thomas Lamprecht
2022-07-13 9:43 ` [pbs-devel] [PATCH proxmox-backup v2 3/4] restore-daemon: add 'format' and 'zstd' parameters to the 'extract' handler Dominik Csapak
2022-10-05 16:54 ` [pbs-devel] applied: " Thomas Lamprecht
2022-07-13 9:43 ` [pbs-devel] [PATCH proxmox-backup v2 4/4] file-restore: add 'format' and 'zstd' parameters to 'extract' command Dominik Csapak
2022-10-05 16:54 ` [pbs-devel] applied: " Thomas Lamprecht
2022-07-13 9:43 ` [pbs-devel] [PATCH common v2 1/1] PBSClient: add 'tar' parameter to file_restore_extract Dominik Csapak
2022-07-13 9:43 ` [pbs-devel] [PATCH storage v2 1/1] api/filerestore: add 'tar' parameter to 'download' api Dominik Csapak
2022-07-13 9:43 ` [pbs-devel] [PATCH widget-toolkit v2 1/1] window/FileBrowser: enable tar button by default Dominik Csapak
2023-10-19 7:20 ` Dominik Csapak [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=5a2d3c7e-1b49-4534-93c6-e61b1aef20bc@proxmox.com \
--to=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