From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Stefan Reiter <s.reiter@proxmox.com>
Subject: [pbs-devel] applied: Re: [PATCH v3 qemu] PVE: Add PBS block driver to map backup archives into VMs
Date: Thu, 9 Jul 2020 13:52:32 +0200 [thread overview]
Message-ID: <dcf40ee7-1957-e060-e1c7-66f8eb1ac4a4@proxmox.com> (raw)
In-Reply-To: <20200708075054.17343-1-s.reiter@proxmox.com>
On 08.07.20 09:50, Stefan Reiter wrote:
> Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
> [error cleanups, file_open implementation]
> Signed-off-by: Dietmar Maurer <dietmar@proxmox.com>
> ---
> block/Makefile.objs | 2 +
> block/pbs.c | 271 +++++++++++++++++++++++++++++++++++++++++++
> configure | 10 ++
> qapi/block-core.json | 14 ++-
> 4 files changed, 296 insertions(+), 1 deletion(-)
> create mode 100644 block/pbs.c
>
>
applied, thanks! (but not tested deeply yet)
prev parent reply other threads:[~2020-07-09 11:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:50 [pbs-devel] " Stefan Reiter
2020-07-09 11:52 ` 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=dcf40ee7-1957-e060-e1c7-66f8eb1ac4a4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.reiter@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