From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Fabian Ebner <f.ebner@proxmox.com>
Subject: [pbs-devel] applied: [PATCH proxmox-backup] client: expose all-file-systems option
Date: Mon, 16 Nov 2020 17:01:29 +0100 [thread overview]
Message-ID: <60ba632b-761e-6911-cde5-c8036da790b4@proxmox.com> (raw)
In-Reply-To: <20201116092247.23491-1-f.ebner@proxmox.com>
On 16.11.20 10:22, Fabian Ebner wrote:
> Useful to avoid the need for a long (and possibly changing) list of include-dev
> options in certain situations, e.g. nested ZFS file systems. The option is
> already implemented and seems to work as expected. The checks for virtual
> filesystems are not affected by this option.
>
> Signed-off-by: Fabian Ebner <f.ebner@proxmox.com>
> ---
> src/bin/proxmox-backup-client.rs | 5 +++++
> 1 file changed, 5 insertions(+)
>
>
applied, thanks!
prev parent reply other threads:[~2020-11-16 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 9:22 [pbs-devel] " Fabian Ebner
2020-11-16 16:01 ` 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=60ba632b-761e-6911-cde5-c8036da790b4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox