From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied: Re: [PATCH manager 1/1] ui: node/ZFS: add zstd to possible compression methods
Date: Fri, 30 Jul 2021 17:08:10 +0200 [thread overview]
Message-ID: <b2a436b4-8e77-173c-e04e-b90ff1c26b67@proxmox.com> (raw)
In-Reply-To: <20210730113416.2326172-3-d.csapak@proxmox.com>
On 30/07/2021 13:34, Dominik Csapak wrote:
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> www/manager6/node/ZFS.js | 1 +
> 1 file changed, 1 insertion(+)
>
>
applied, with d/control version bump for storage as follow up, thanks!
prev parent reply other threads:[~2021-07-30 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 11:34 [pve-devel] [PATCH storage/manager] allow zstd compression for new zpools Dominik Csapak
2021-07-30 11:34 ` [pve-devel] [PATCH storage 1/1] api: disks: allow zstd compression for zfs pools Dominik Csapak
2021-07-30 13:37 ` [pve-devel] applied: " Thomas Lamprecht
2021-07-30 11:34 ` [pve-devel] [PATCH manager 1/1] ui: node/ZFS: add zstd to possible compression methods Dominik Csapak
2021-07-30 15:08 ` 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=b2a436b4-8e77-173c-e04e-b90ff1c26b67@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@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